Connect Basin to any MCP client
Basin is an MCP server. Any client that can add a remote MCP server will work. This is the honest answer to whether it works with the tool you use: if your client supports the two things below, yes.
Plan requirements and settings paths last checked 8 September 2026
If your tool has its own guide, start there
These have step-by-step pages of their own, with the settings paths and the plan requirements:
What your client needs to support
- Remote MCP over Streamable HTTP. Basin does not serve the older SSE transport.
- OAuth 2.0. Basin signs you in through a standard OAuth flow with a consent screen. No API key to paste.
The endpoint
Point your client at it as a remote MCP server and complete the sign-in. You do not need a Basin account first: you enter your email, Basin sends a code, and you are in. The code expires in 10 minutes.
When you connect, Basin asks for two things: read access to the spaces you own and the ones shared with you, and write access to files in those spaces, stamped with your email. Connecting shares nothing with anyone else. Sharing is always a separate step.
Shortcuts, where the client documents one
Cursor has a one-click install — use the Cursor page for that. VS Code, and GitHub Copilot inside it, take a single command:
code --add-mcp '{"name":"basin","type":"http","url":"https://mcp.getbasin.co/mcp"}'Both do the same thing as pasting the endpoint by hand. Every other client adds it through its own settings screen or config file.
After you connect
Start a new session or reload, so the client loads Basin's tools. A session that was already open will not see them.
Then add these instructions wherever your client keeps persistent instructions:
Check Basin at the start of every conversation.
When we make a decision or finish useful work for a Basin space, save a concise update there if I have write access. Include only information intended for the people with access. Ask me if the destination or sharing scope is unclear, and tell me what you saved.
Without it the assistant may not think to look. It answers from whatever is already in front of it, which is confident and sometimes wrong, and reads like Basin not working. Basin is a live connector, not a document in the session. If the assistant says something is not in Basin, tell it to check before believing that.
Check the connection
The first time your assistant uses Basin, your tool will ask your permission to run it. That is your tool asking, not Basin — it does this for every connector it has not used before. Approve it to carry on. Nothing reaches Basin until you do.
A successful response from Basin confirms the connection. If your library is empty, that's fine—your next step is to save a project.
If it did not work
Put it to work.
Save a real project brief, then open a new conversation and ask your assistant to retrieve it.