Mcp Api
Expose GoMarble’s hosted API to your coding agent through MCP so you can call GoMarble capabilities from the IDE without bespoke HTTP glue each session.
Overview
GoMarble MCP API is an MCP server for the build phase that exposes GoMarble’s hosted API to agents via an SSE remote endpoint.
What is this MCP server?
- Hosted SSE MCP remote at apps.gomarble.ai/mcp-api/sse
- GoMarble-branded MCP API server (version 1.0.0)
- No local package manifest in catalog—remote-only consumption
- Suited for agent-side calls to GoMarble HTTP APIs via MCP tool surface
- Minimal configuration surface for quick MCP client registration
- Remote transport: SSE at https://apps.gomarble.ai/mcp-api/sse
- Catalog server version 1.0.0
What problem does it solve?
Agents waste time re-implementing GoMarble HTTP calls and auth headers when you need the same API actions from every coding session.
Who is it for?
Builders already using GoMarble who want MCP-native access from Claude Code or similar clients and accept a hosted remote dependency.
Skip if: Anyone needing full tool documentation, self-hosted MCP, or clear journey placement without reading GoMarble’s separate API docs.
What do I get? / Deliverables
Registering the GoMarble SSE MCP remote gives your agent a stable tool channel to GoMarble’s API instead of ad-hoc REST snippets.
- SSE MCP remote registered in agent config
- Agent-invokable GoMarble API tool surface (per server capabilities)
- Less manual HTTP orchestration for GoMarble tasks
Recommended MCP Servers
Journey fit
Listed on the build integrations shelf because the entry is a thin remote API bridge—primary value is wiring an external GoMarble service into agent workflows during product construction. Integrations subphase fits hosted SSE MCP endpoints that standardize how agents authenticate and invoke a vendor API.
How it compares
Vendor API MCP bridge over SSE, not a documented multi-step agent skill or local stdio server.
Common Questions / FAQ
Who is ai.gomarble/mcp-api for?
Developers and solo builders who use GoMarble services and want their MCP agent to reach those APIs through the official hosted MCP API server.
When should I use ai.gomarble/mcp-api?
Use it during build when you are integrating GoMarble into your product or internal tools and prefer MCP tool calls over manual HTTP from the agent.
How do I add ai.gomarble/mcp-api to my agent?
Configure your client with the SSE remote URL https://apps.gomarble.ai/mcp-api/sse and supply any API keys or OAuth GoMarble requires outside this catalog entry.