Manus Custom MCP Servers: add Sume under Settings > Integrations
In Manus, open Settings > Integrations > Custom MCP Servers > Add Server and enter Sume's HTTPS endpoint and credentials. Manus verifies by fetching tools.
Open Settings > Integrations > Custom MCP Servers in Manus, click Add Server, give it a name, set the endpoint to https://mcp.sume.com/mcp, and supply credentials. Manus's page lists three fields: server name, HTTPS endpoint, and authentication credentials (API keys, OAuth tokens or other credentials), and says Manus verifies the connection by retrieving the tool list.
Manus's steps are from its Custom MCP docs; Sume's from the MCP quickstart and OAuth and API keys, read 2026-10-06. Sume has no official Manus integration.
What does the check prove?
Retrieving the tool list proves that the endpoint is reachable and the credential is accepted. It does not show which tools your credential can use for writes or paid work. After connecting, ask the agent to call mcp_health and read the auth source and safety posture it reports, then tools_list for what this session sees.
| Manus field | Value for Sume | Note |
|---|---|---|
| Server name | Any label, for example Sume | Shown in your Manus tool list |
| Endpoint | https://mcp.sume.com/mcp | Manus asks for HTTPS |
| Credentials | API key as Bearer or x-api-key | Keep it out of URLs and logs |
| Verification | Manus fetches the tool list | Run mcp_health as well |
Credential hygiene
Manus's page tells you to use HTTPS and never to expose credentials in URLs or logs. Sume's safe-automation guidance matches: log request ids and job ids, not keys. Never put a Sume key in the endpoint URL as a query string.
Sources
Related posts
More in Integrations
- Is mcp.dev.sume.com a staging URL I can use? No, use mcp.sume.com
mcp.dev.sume.com is for Sume's own development environments. Customer configs should use https://mcp.sume.com/mcp, and OAuth tokens are bound to that resource.
- Meta Muse Zapier connector: how do I limit what an agent can spend?
Zapier's Muse connector brokers app access over Zapier MCP. Spend limits live in each tool you expose. Here is how Sume's scopes, caps and idempotency keys fit.
- provider.only on Sume image requests: why other slugs return 400
Porting an OpenRouter-style image call? On Sume, provider.only and order accept only sume; other slugs return 400 provider_not_available. Field rules.
- Render a Short over MCP: timeline_create, jobs_wait, timeline_get
Three hosted MCP tool calls turn a Timeline document into a vertical Short: create with an idempotency_key, wait on the job, then fetch the result.
Written by Sume