Hosted at [curve.mcp.junct.dev/mcp](https://curve.mcp.junct.dev/mcp). Free to use. No auth. No API key required.
Curve MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Curve MCP directly instead of describing what you should do. Hosted at curve.mcp.junct.dev/mcp. Free to use. No auth. No API key required.
This MCP server is deterministically generated from the Curve API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Curve MCP is connected, these are the calls the assistant has available:
Protocol — ** CurveEndpoint — ** https://curve.mcp.junct.dev/mcpTransport — ** Streamable HTTPAuth — ** None requiredDocumentation — ** curve.mcp.junct.dev/llms.txtThis 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. Curve 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.
This entry was verified against Curve MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Protocol | ** Curve |
| Endpoint | ** https://curve.mcp.junct.dev/mcp |
| Transport | ** Streamable HTTP |
| Auth | ** None required |
| Documentation | ** [curve.mcp.junct.dev/llms.txt](https://curve.mcp.junct.dev/llms.txt) |
{
"mcpServers": {
"curve": {
"url": "https://curve.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.