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 29 August 2026

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

Endpointhttps://mcp.getbasin.co/mcp

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 one line wherever your client keeps persistent instructions:

Check Basin at the start of every conversation.

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.

Verify

Ask for something that needs a real read:

What is in my Basin library?

If it names your spaces, it is working.

If it did not work

No Basin tools at all.The client did not establish the session. Confirm it supports remote MCP over Streamable HTTP, and that the OAuth sign-in completed.

Fewer than 17 tools.The client is holding an old tool list. Reconnect. Basin serves 17 tools; fewer means the list is stale.

The tools are there but the assistant never uses them.The standing instruction above is missing, or the client keeps tool details behind a search until something asks. Add the line, or load Basin's tools eagerly if your client offers that. This one does not look like a connection problem, which is why it is the common one.