Custom MCP servers

Sokko supports custom MCP servers as well as Composio's app catalogue. An app missing from Composio may still offer an MCP server you can configure yourself. Adding a compatible server does not require a Sokko engineer.

Add a configuration from chat

Ask your agent to add the provider's documented MCP configuration. You can give it the non-secret URL, or a local command and arguments. The agent should verify the provider documentation and check its current Sokko capabilities first.

For a remote server, provide its HTTP endpoint and authentication method. Sokko supports unauthenticated endpoints, bearer tokens, and custom headers on ports 443 and 80. Do not include credentials in the URL or a chat message.

For a local server, provide the executable, arguments, and the names of any environment variables it needs. Sokko runs stdio servers inside the agent's runtime. The executable, packages, driver files, and any required licences must be available there. A GitHub repository URL is not a remote MCP endpoint.

Your agent uses sokko_add_mcp_server to register the configuration. Servers without credential fields are saved immediately. For servers requiring credentials, it sends a private setup link that expires after 30 minutes. Open that link, review the server and target agent, and enter the requested values. This page needs no Sokko login. Credentials go into Vault and are provided only to the agent granted that server; they are not returned to chat. Keep the full link private: anyone who receives it can complete that setup before it expires or is used. Ask for a fresh link to invalidate a previous one.

The configuration is saved in Sokko's MCP registry and granted to the calling agent. Existing skills, secrets, other MCP servers, and channel settings are preserved. Registering a new MCP can restart the agent to load its tools.

Return to the same chat when setup finishes. The agent checks sokko_mcp_server_status, discovers the server's runtime tools, and tests a read-only action. A saved configuration alone does not verify the provider credentials, network access, or local command. Those checks must succeed before the agent says the integration works.

Examples for agents

The customer asks to register a verified remote endpoint with bearer auth:

{
  "name": "company-mcp",
  "transport": "http",
  "url": "https://mcp.example.com/mcp",
  "authKind": "bearer"
}

This is an example URL, not an actual provider endpoint. Use the customer's or provider's verified URL. Share the returned setupUrl for credential entry.

For a verified local command, use transport: "stdio", command, args, and an env array containing variable names. Likewise, headers is an array of HTTP header names. Neither array accepts credential values through the tool. All those values are entered on the private setup page.

Before recommending a Java-based connector, for example, verify Java and its driver are present. If they are missing, explain the prerequisites and help prepare them after the customer's request. Do not report that Sokko lacks MCP support because a particular runtime dependency has not been installed.

Existing servers and permissions

sokko_mcp_servers lists only the calling agent's custom MCP configurations and chat setup attempts. Chat cannot overwrite an existing library server, change another agent, or restore a grant an administrator revoked. Retry an expired or failed setup by asking the agent to add the same configuration again.

Owners and admins can also add or edit servers in MCP servers and grant them to other agents. Custom MCP support is separate from the Composio Connected apps switch and its paid-plan requirement. Use sokko_capabilities to check whether the current runtime supports it.

For other Sokko questions, agents should read sokko_docs and check live capabilities before claiming the platform cannot perform an action.