Developer MCP guide

Developer MCP is the coding-agent schema surface hosted by the same Gateway /mcp implementation used by Platform /api/mcp and Platform Playground. Agents can list visible providers, search operations, fetch schema bundles, and ask for integration guidance through read-only apifuse_dev_* tools, while provider execution remains behind the runtime execution flow and server-side ApiFuse APIs.

Configure a coding agent

Register the hosted ApiFuse MCP endpoint in clients that support HTTP MCP transport. Use the environment-specific Platform MCP URL; it proxies the canonical Gateway /mcp implementation.

{
  "mcpServers": {
    "apifuse-developer": {
      "url": "https://apifuse.com/api/mcp",
      "transport": "http"
    }
  }
}

For local development, use the Platform app origin. The route at apps/platform/app/api/mcp/route.ts is a thin proxy to Gateway /mcp.

{
  "mcpServers": {
    "apifuse-developer-local": {
      "url": "http://localhost:3000/api/mcp",
      "transport": "http"
    }
  }
}

Supported workflow

1. Call apifuse_dev_list_providers to inspect public provider summaries.
2. Call apifuse_dev_search_operations or apifuse_dev_list_capabilities to find candidate operations.
3. Call apifuse_dev_get_operation_spec for exact input/output JSON Schemas, auth mode, artifact version, and hashes.
4. Call apifuse_dev_get_schema_bundle for generated JSON Schema, OpenAPI, TypeScript, Zod, or Pydantic artifacts.
5. Call apifuse_dev_get_integration_guide for deterministic server-side snippets.
6. Implement runtime calls in your application server using ApiFuse Gateway/API Reference paths, not through Developer MCP.

Tool contract summary

Compatibility fallback

Developer MCP responses include serialized JSON text so older tools/list and tools/call clients can parse results without structured-output support. Newer clients may also receive structured content when supported, but the serialized JSON fallback remains the compatibility contract.

What Developer MCP does not do

• It does not execute provider operations.
• It does not expose call_*, execute_*, invoke_*, dispatch, proxy, credential, revoke, update, or delete tools.
• apifuse_dev_* calls do not invoke provider dispatch/proxy handlers, credential RPC clients, or Connection mutation APIs.
• It does not accept, resolve, or return canonical Connection identifiers.
• It does not reveal private, internal, beta, removed, or unclassified providers through public search, counts, hashes, ETags, cache keys, or error messages.

Runtime execution path

After your agent has generated code from Developer MCP artifacts, execute operations from server-side application code through the documented ApiFuse Gateway/API Reference path or the guarded runtime MCP execution flow. Keep API keys and any tenant auth mapping on the server. Do not forward secrets, artifact administration data, or tenant connection references to browser clients.