Hosted at [synthetix.mcp.junct.dev/mcp](https://synthetix.mcp.junct.dev/mcp). Free to use. No auth. No API key required.
Hosted at synthetix.mcp.junct.dev/mcp. Free to use. No auth. No API key required. That is what the synthetix mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This MCP server is deterministically generated from the Synthetix API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 5 tools. What each one is for:
Protocol — ** SynthetixEndpoint — ** https://synthetix.mcp.junct.dev/mcpTransport — ** Streamable HTTPAuth — ** None requiredDocumentation — ** synthetix.mcp.junct.dev/llms.txtPlenty of knowledge and memory 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. Synthetix MCP's toolset — Protocol, Endpoint, Transport and 2 more — is a fair guide to whether it matches your workflow. It is maintained by junct-bot; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Protocol | ** Synthetix |
| Endpoint | ** https://synthetix.mcp.junct.dev/mcp |
| Transport | ** Streamable HTTP |
| Auth | ** None required |
| Documentation | ** [synthetix.mcp.junct.dev/llms.txt](https://synthetix.mcp.junct.dev/llms.txt) |
{
"mcpServers": {
"synthetix": {
"url": "https://synthetix.mcp.junct.dev/mcp",
"transport": "streamable-http"
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.