Skip to content

Connect your agent

Senvi runs its own OAuth server. Connecting means approving Senvi in a browser window, the way you approve any other app. There is no API key and nothing to paste.

The line below tells you where your own account stands.

Sign in to see whether your agent is connected.

One note on price before you start.

Connecting is free, and so is the first session where your agent sets you up (setup prompt and onboarding intake). The weekly loop, which is refinement, sprint plan and retro, needs a plan or the 7-day trial that starts when you sign up.

Find your agent

Pick the one you use. If yours is not named, the last entry covers it.

Claude Code

We have not connected from this client ourselves yet.

Who this is for. You run Claude Code in a terminal.

Where the setting lives. Your terminal for the install, then /mcp inside a Claude Code session for the approval.

Steps. Four, and only the last one leaves the terminal.

  1. Install the Senvi plugin with the two commands below.
  2. Run /mcp in a Claude Code session.
  3. Pick Senvi from the list it shows.
  4. Approve the connection in the browser window that opens.

The two commands:

claude plugin marketplace add ebisong/senvi-marketplace
claude plugin install senvi@senvi

What the approval looks like. A Senvi page on senvi.ai, asking you to allow the connection and naming the account you are signed in as. It is our page, not a third party's, and nothing on it asks you for a key.

How to tell it worked. /mcp lists Senvi as connected, and the connection line at the top of this page flips on its own.

What to say to start. set up Senvi

The Claude apps

We have not connected from this client ourselves yet. The steps below come from the vendor's own documentation.

Who this is for. You use Claude in the desktop app, at claude.ai, or on your phone. It is one set of steps for all three, because it is one mechanism.

Where the setting lives. Settings, then Connectors, then "Add custom connector".

Steps. Four, and you do them once for the whole account.

  1. Open Settings, then Connectors, and choose "Add custom connector".
  2. Paste the Senvi server URL below into the remote MCP server field.
  3. Approve the connection in the browser window that opens.
  4. Turn Senvi on in the chat's tool list, so your assistant can reach it.

The URL to paste:

https://mcp.senvi.ai/api/mcp

What the approval looks like. The same Senvi page in a browser window, asking you to allow the connection.

How to tell it worked. Senvi appears in your connector list, and its tools appear in the chat once you switch them on.

What to say to start. set up Senvi

Custom connectors are available on Free, Pro, Max, Team and Enterprise. Two of Anthropic's rules can still get in the way. A free account gets one custom connector at a time, and on Team and Enterprise only an Owner can add one.

Add it anywhere and it works everywhere, phone included. A custom connector is brokered from Anthropic's own infrastructure rather than from the machine in front of you, so what you connected is the account, not the laptop.

Cursor

We have not connected from this client ourselves yet. The steps below come from the vendor's own documentation.

Who this is for. You work in Cursor.

Where the setting lives. A file. Cursor takes a url entry in .cursor/mcp.json for one project, or the same entry in ~/.cursor/mcp.json for every project you open.

Steps. Three, and the last one happens in your browser.

  1. Open .cursor/mcp.json in the project, or create it if there is none.
  2. Add Senvi as a server, with the address below as its url.
  3. Let Cursor connect, and approve in the browser window it sends you to.

The address:

https://mcp.senvi.ai/api/mcp

What the approval looks like. The same Senvi page in a browser window, asking you to allow the connection.

How to tell it worked. Cursor lists Senvi's tools under the server.

What to say to start. set up Senvi

There is nothing else to set up. Cursor speaks Streamable HTTP and OAuth, and Senvi hands out its own credentials to a client that asks, so there is no key to copy and no field to fill in.

Any other MCP client

Who this is for. Anything that speaks MCP and can do OAuth, including clients we have never opened.

Where the setting lives. Wherever your client adds a remote MCP server. We have not seen that screen, so we are not going to name a menu that might not be there.

Steps. Two. There is no third one.

  1. Add Senvi as a remote MCP server over streamable HTTP, at the address below.
  2. Approve the connection in the browser window that opens.

The address:

https://mcp.senvi.ai/api/mcp

What the approval looks like. The same Senvi page in a browser window, asking you to allow the connection.

How to tell it worked. Your client lists Senvi's tools.

What to say to start. set up Senvi

Senvi runs its own OAuth server, with open dynamic client registration and PKCE. Your client registers itself and collects its own credentials, so there is no key for us to issue and nothing for you to paste.

If a client will not register at all, the discovery documents are the place to start. They sit at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource on the server address above.

Where the coaching comes from

Your agent fetches the coaching from Senvi at the start of each session, so it stays current and it stops when a plan stops. It arrives as ordinary text in your agent's context, with one line naming the account it was served to.

What next

The weekly loop is what you do once the first session is done.

Troubleshooting is where to go if the approval did not take, or if your agent connected and then acted like it had never heard of us.

Sources