That's it. The response contains everything you need to sign and broadcast.
If you already use Swap Api, the swap api mcp server is the piece that lets your assistant work with it directly. That's it. The response contains everything you need to sign and broadcast.
@swapapi/mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Param — RequiredchainId — pathtokenIn — querytokenOut — queryamount — querysender — querymaxSlippage — queryConfiguration is passed through the environment: CHAIN_ID, PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Swap Api's toolset — Param, chainId, tokenIn and 4 more — is a fair guide to whether it matches your workflow. It is maintained by swap-api; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Param | Required |
| chainId | path |
| tokenIn | query |
| tokenOut | query |
| amount | query |
| sender | query |
| maxSlippage | query |
Or add to Claude Desktop config:
```json
{
"mcpServers": {
"swapapi": {
"command": "npx",
"args": ["@swapapi/mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHAIN_ID | Configuration value read at startup. | Optional |
| PRIVATE_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.