Hosted at [chainlink.mcp.junct.dev/mcp](https://chainlink.mcp.junct.dev/mcp). Free to use. No auth. No API key required.
Hosted at chainlink.mcp.junct.dev/mcp. Free to use. No auth. No API key required. Exposed over MCP by the chainlink mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This MCP server is deterministically generated from the Chainlink API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
Everything the assistant can do here goes through one of these:
Protocol — ** ChainlinkEndpoint — ** https://chainlink.mcp.junct.dev/mcpTransport — ** Streamable HTTPAuth — ** None requiredDocumentation — ** chainlink.mcp.junct.dev/llms.txtBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chainlink 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.
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 |
|---|---|
| Protocol | ** Chainlink |
| Endpoint | ** https://chainlink.mcp.junct.dev/mcp |
| Transport | ** Streamable HTTP |
| Auth | ** None required |
| Documentation | ** [chainlink.mcp.junct.dev/llms.txt](https://chainlink.mcp.junct.dev/llms.txt) |
{
"mcpServers": {
"chainlink": {
"url": "https://chainlink.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.