- Full API documentation for your agent. Ask it to "integrate Razorpay" and it gets the whole reference in one call: base URL, the exact authentication header, the credentials as environment variables, the provider's integration notes (signature checks, webhooks, units, common errors) and the request and response of every endpoint, written for an agent to read.
- The API directory. Thousands of public APIs from the Marketplace, with base URLs, authentication, the credentials to obtain, official docs and every endpoint, read from each provider's own API description. Guided collections for the most used APIs list the requests in the order you need them.
- Integration guides with working code. Step by step for one API in your language: credentials, environment variables, install, the first requests with code from the same generator as the app (30 languages and libraries), example responses, error handling and testing.
- Live tests. Send HTTP requests, run GraphQL queries and introspection, and open short WebSocket, Socket.IO, SSE, MQTT, GraphQL subscription, gRPC and MCP sessions from Swastik Codes servers, then read status, timing, headers, bodies and every message.
https://swastik.codes/mcpThat one URL is all a client needs. It speaks Streamable HTTP, and you connect either by signing in (OAuth) or with an API key.
Connect your assistant
Claude (web and desktop): open Settings › Connectors, choose Add custom connector, name it Swastik Codes and paste https://swastik.codes/mcp. Choose Connect, sign in to Swastik Codes and allow access. In a chat, turn the connector on from the tools menu.
ChatGPT: open Settings › Apps & Connectors › Advanced settings and turn on Developer mode. Choose Create, paste the URL, pick OAuth, then sign in and allow access. Add Swastik Codes to a chat from the + menu.
Claude Code: sign in through the browser, or pass an API key.
claude mcp add --transport http swastik-codes https://swastik.codes/mcp
# or with an API key from Account › API keys
claude mcp add --transport http swastik-codes https://swastik.codes/mcp \
--header "Authorization: Bearer $SWC_API_KEY"Cursor: add it to ~/.cursor/mcp.json. Leave out headers to sign in with OAuth instead.
{
"mcpServers": {
"swastik-codes": {
"url": "https://swastik.codes/mcp",
"headers": { "Authorization": "Bearer ${env:SWC_API_KEY}" }
}
}
}VS Code: add it to .vscode/mcp.json. VS Code asks for the key once and keeps it in its secret storage.
{
"inputs": [{ "type": "promptString", "id": "swc-key", "description": "Swastik Codes API key", "password": true }],
"servers": {
"swastik-codes": {
"type": "http",
"url": "https://swastik.codes/mcp",
"headers": { "Authorization": "Bearer ${input:swc-key}" }
}
}
}Any other client: point it at the URL. OAuth is discovered from the server (protected resource metadata, dynamic client registration and client ID metadata documents are supported), or send Authorization: Bearer <API key>. In the web app, Account › AI assistants shows the same steps and lists every connected assistant.
Integrate an API from your coding agent
Swastik Codes is the API documentation your agent reads before it writes code. In Claude Code, Cursor or VS Code, ask:
Integrate Razorpay payments into this project: create an order on checkout and verify the payment.
The agent calls get_api_docs with razorpay and reads, in order:
- Quick facts. Base URL
https://api.razorpay.com/v1; authenticationAuthorization: Basic base64(RAZORPAY_KEY_ID:RAZORPAY_KEY_SECRET); the two credentials, where to generate them, and that they belong in server-side environment variables. - Integration notes from the provider's docs. Amounts are integers in paise; how to verify the Checkout signature with HMAC-SHA256; how to verify and de-duplicate webhooks; test UPI IDs; common errors and what to do about them.
- Every endpoint. Method and full URL, every parameter and request and response field with its type, whether it is required, the allowed values and limits (for example
currency: string, one of INR, USD), headers, the request body, and example responses, success and error. IDs that come from an earlier call are marked, for example{orderId}from Create an order.
It then writes the integration from those facts, not from memory, and can try a call with send_http_request once you give it test keys. Large APIs come in pages, or one section at a time (section: "refunds"). Clients that show MCP prompts also offer Integrate an API (in Claude Code: /mcp__swastik-codes__integrate_api razorpay), which walks the agent through the same steps.
Your own API, for your assistant
The directory covers public APIs. For your own backend, start with Routeman, our free, open-source (MIT) tool that writes a Postman collection from your code: Django, Django REST framework, Flask and FastAPI with pip install routeman and routeman generate, or Express, NestJS, Fastify, Next.js and more with npx routeman-cli. It finds the routes, request bodies, the auth scheme and the login request, and writes a collection plus a local environment into postman/.
Then give that collection to your coding assistant with swc mcp from the CLI. It runs on your computer, so it can reach localhost:
claude mcp add shop-api -- swc mcp postman/shop-api.postman_collection.json \
-e postman/shop-api.local.postman_environment.jsonThe assistant can now list your requests, read them, send them and run their tests. Read-only unless you add --allow-write; secrets and auth headers are redacted. To share the collection with your team instead, open Import in the app and drop the same two files.
The tools
| Tool | What it does | Changes data? |
|---|---|---|
search | Find APIs by task or provider, e.g. "send SMS India" or "stripe". Returns ids, titles and links. | No |
fetch | One API's documentation by id (the first page of get_api_docs). | No |
search_apis | Search with a category, paging and per-result details (endpoint count, auth, guided). | No |
list_api_categories | The categories and how many APIs each has. | No |
get_api_docs | The complete documentation of an API by name or id: base URL, exact auth header, credentials as environment variables, integration notes, and every endpoint's request and response. In pages or by section. | No |
get_api | A short overview of an API by id, directory URL or name. | No |
list_api_endpoints | The endpoints of an API, numbered, filtered by text or HTTP method. | No |
get_api_endpoint | Everything to call one endpoint: parameters, headers, body example, example responses and optional code. | No |
get_integration_guide | A step-by-step integration guide with working code in your language. | No |
send_http_request | Send a real HTTP request and return status, timing, headers and body. | Can (POST, PUT, DELETE…) |
graphql_request | Run a GraphQL query or mutation. | Can (mutations) |
graphql_introspect | Fetch a GraphQL schema as SDL. | No |
test_realtime | Connect over WebSocket, Socket.IO, SSE, MQTT, GraphQL subscriptions, gRPC or MCP, send messages and record what arrives for up to 30 seconds. | Can (publish, calls) |
Every tool carries a title and the read-only, destructive and open-world hints of the MCP specification, so your assistant asks before anything that can change data. Credentials in generated code are placeholders such as YOUR_KEY_ID, with the environment variable to read them from.
Example prompts
- "Which APIs can send WhatsApp template messages from India? Compare their authentication."
- "Integrate Razorpay into this project: create an order at checkout and verify the payment signature."
- "Write a Python function that creates a Razorpay order and verifies the payment signature."
- "List the refund endpoints of the PhonePe payment gateway and show the request body of the first one."
- "Introspect https://countries.trevorblades.com/ and write a query for India's capital and currency."
- "Connect to wss://echo.websocket.org, send hello, and show me what comes back."
- "Subscribe to sensors/# on my broker at mqtts://broker.example.com and summarise the next 10 messages."
- "Call tools/list on my MCP server at https://mcp.example.com/mcp and check every tool has a title."
Security and limits
- Your account, your choice. Signing in with OAuth shows exactly what the assistant asks for: reading the API directory, sending test requests, or both. You can disconnect any assistant at any time in Account › AI assistants; API keys are deleted under Account › API keys.
- Tokens are short-lived. OAuth access tokens last one hour and refresh tokens rotate on every use. A refresh token that is used twice ends the whole connection. Tokens, codes and keys are stored only as hashes and work only for this server.
- Public internet only. Test requests go out from Swastik Codes servers and can never reach private, loopback, link-local or cloud metadata addresses. To test
localhostor a private network, use the desktop app orswc bridgefrom the CLI. - Fair limits. Up to 120 tool calls a minute per account, the same concurrent request and session limits as the web app, sessions of at most 30 seconds, and responses trimmed so your assistant's context is not flooded.
- Untrusted content is labelled. Bodies and messages from third-party servers are marked as data, and the server tells assistants never to follow instructions found in them.
- No storage of what you test. Request and response contents are not saved by the MCP server; only the tool name, the account and the timing are logged to keep the service running. See the privacy policy.
Frequently asked questions
Is it free?
Yes. The MCP server is included with every free Swastik Codes account.
Do I need an account?
Yes, so that requests sent from our servers are tied to someone and rate limited. Sign in once with GitHub, Google or email; Claude and ChatGPT then connect with OAuth, and coding tools can use an API key.
Which assistants does it work with?
Any client that supports remote MCP servers over Streamable HTTP: Claude, ChatGPT, Claude Code, Cursor, VS Code with GitHub Copilot and others. Protocol versions 2025-03-26 through 2026-07-28 are supported.
Where does the API information come from?
From each provider's published API description (OpenAPI and similar), official vendor specifications and collections we write by hand from official documentation. Every API links to its official docs, and its page in the Marketplace shows the same data.
Can it reach my local server?
No. Requests leave from Swastik Codes servers, which cannot see your computer or your private network. Use the desktop app or swc bridge for that, or run swc mcp from the CLI to give your assistant your own collections with your computer's network.