Quickstart

SourceMCP turns an OpenAPI, Swagger or Postman spec into a hosted MCP server. You pick the endpoints, and AI clients such as Cursor, Claude and VS Code call your real API through one MCP URL. This takes about ten minutes.

1. Create an account

Sign up with email or a social login. Every account gets the same limits.

2. Upload your spec

Open New server and upload a file (JSON or YAML: OpenAPI 3.x, Swagger 2.0 or a Postman collection) or paste a URL to it. SourceMCP reads the spec and lists every operation it found, with warnings for anything it couldn't use.

3. Pick the endpoints

Each endpoint becomes one tool. Small specs start with everything selected; for larger ones, choose the endpoints an assistant actually needs. Fewer, well-named tools work better: rename a tool or rewrite its description so the model knows when to call it.

4. Set the base URL and credentials

Confirm the base URL your API lives at, then tell SourceMCP how to authenticate to it:

• Static credentials: headers (such as Authorization or X-API-Key) or query parameters. They are encrypted and never shown again.
• Sign in to the API: for APIs with a login endpoint instead of a key, you sign in once and SourceMCP keeps the tokens the API returns. See API keys and OAuth.

5. Connect a client

The last step shows your MCP URL, a one-time API key and ready-to-copy snippets. Paste one into your client (see Connecting clients) and ask the assistant to use the API.

6. Test and watch

• The Playground tab calls a tool with a form, exactly as an AI client would.
• The Logs tab shows every call, its status and how long it took.
• The Tools tab lets you change which endpoints are exposed at any time; clients pick up the change on their next request.