Connection & Setup
Connecting your assistant
The MCP server of SESAM is available at:
| Text Only | |
|---|---|
The setup depends on your assistant. The following examples show two common ones. Other clients that support remote MCP servers with OAuth work the same way: add a server of type HTTP (also called Streamable HTTP) with the URL above.
Claude Code
| Bash | |
|---|---|
Then start claude and run /mcp to log in to the sesam server.
Visual Studio Code
Add the server to your mcp.json (command MCP: Open User Configuration):
| JSON | |
|---|---|
VS Code starts the login when the server is started for the first time.
Logging in
When you connect for the first time, your browser opens the SESAM login page:
- Log in with your SESAM account, if you are not logged in yet.
- SESAM shows which application asks for access. Check it and confirm.
- The browser sends you back to your assistant, which is now connected.
Your SESAM password is never shared with the assistant. The assistant only receives a temporary access token for your account.
Note
The assistant gets the access sesam, which allows it to use all tools on your behalf. Only connect assistants that you trust.
Troubleshooting
The login page does not open.
: Check that your assistant supports remote MCP servers with OAuth and that the URL is exactly https://sesam.co4e.com/mcp.
The assistant reports that an action is not available on your plan. : Ask the assistant for your plan and quota, or have a look at your plan in the account settings.
Tools are missing. : Reconnect the server in your assistant, so that it reloads the tool list.
If something does not work as expected, send us a message via the feedback form.