Agents

Uteke for Composio

Composio · Automation · MCP + API key · Beta

An integration platform that turns remote MCP servers into toolkits for your agents.

Beta: written from Composio's own documentation and not tested by us yet. If a step does not match what you see, follow Composio's docs and tell us at [email protected].

Set it up

  1. Create an API key at API keys in the Uteke portal; read-only if the toolkit only recalls.
  2. In Composio, choose Add Custom MCP, name it Uteke Cloud and enter the MCP server URL:
    MCP server URL 
    https://uteke.app/mcp

  3. For authentication choose the option that sends a bearer token or custom header, not DCR OAuth, and set the header to:
    Header 
    Authorization: Bearer utk_live_YOUR_KEY

API keys are made at API keys in the portal; choose read-only if the agent only needs to recall. A key works only for your workspace.

Composio's DCR OAuth mode registers a client dynamically, which Uteke's sign-in does not offer (CodeCora ID registers clients by CIMD only), so it fails even with the right metadata URL. The exact name of the header option may differ in your Composio version.

Try it

Ask Composio:

  • Remember that we release from main only, never from develop.
  • What did we decide about pricing last week?
  • Save this summary to the team room.

Then ask the same thing from another agent you connected: they share one memory.

Disconnect

Open Agents in the portal and choose Disconnect. It works for agents that signed in and for API keys; access is checked again within about 30 seconds. You can also remove Uteke in Composio's own settings.

Composio's documentation on MCP servers: https://docs.composio.dev

Other agents: see all agents or the general steps.