MCP servers with an agent

Use the Core MCP to create and address a customer-published MCP server. The management connection is https://api.requestrocket.com/mcp; end-user agents connect to the regional URL returned by get_mcp_url.

Call get_guide with guide_key: "mcp-creation" before the first create.

Call order

1. Call create_mcp.
   • Required: clientId, mcpName, mcpRegion.
   • Proxy-backed mode: mcpProxyId.
   • Direct mode: mcpProxyCredentialId, mcpTargetId, mcpTargetCredentialId.
   • Optional: mcpAlias, mcpActive, mcpNotes.
2. Keep the returned server sKey.
3. Call get_mcp_url with required mcpId and mcpRegion. stage is optional and should normally be omitted.
4. Connect the end-user MCP client to the returned URL with the configured inbound credential.

Use list_mcps(clientId) to discover ids and get_mcp(clientId, mcpId) to inspect a server. update_mcp requires clientId and mcpId; its other arguments are optional. delete_mcp(clientId, mcpId) is always registered and removes the server, not its backing records.

Example

{
  "tool": "create_mcp",
  "arguments": {
    "clientId": "b3a1c7d2-5e44-4f0a-9c1e-7d2f8a6b1c90",
    "mcpName": "HTTPBin tools",
    "mcpRegion": "us-east-2",
    "mcpProxyId": "5d8a1c30-4e72-4b19-8f6a-0c3d9e7b1a25",
    "mcpActive": true
  }
}

The result contains mcps[0].sKey. Pass that id and us-east-2 to get_mcp_url; the result contains url.

Previewing tools from an OpenAPI document is a Core API call, on the API page. The agent does not have a separate preview tool.

Next