MCP Remote Control
Let another agent drive your signed-in browser
Sidekick Pro speaks the Model Context Protocol from both ends. Connect an MCP client such as Claude Code or Cursor, send your assistant a message, and it does the job in the Chrome you are already signed in to, then reports back.
Included in Personal, from $59 a month Cancel anytime
In short
What is MCP remote control?
MCP remote control means another AI client drives your assistant over the Model Context Protocol. Sidekick Pro runs an MCP server at https://sidekickpro.com/mcp. A connected client sends a plain-English message with the messageSidekick tool, and Sidekick Pro carries it out with every tool it has, including clicking and typing in your own signed-in Chrome, then returns the answer.
What the MCP server gives a client
- One tool, plain English The client sends a sentence with messageSidekick, not a filled-in schema. The assistant works out which of its own tools the job needs.
- Your inbox, inside the chat showSidekickView shows your Sidekick Pro inbox right in ChatGPT, Claude and other apps that show interactive views. Elsewhere it comes back as text.
- Your real browser With the Chrome extension connected, the job runs in your own Chrome, on the sites you are signed in to. No separate credentials to hand over.
- Long jobs do not block When a turn outlives the call, the reply carries the work so far and a checkId. The client collects the finished answer by calling messageSidekick again with that checkId.
- Files, not pasted text Ask for an upload link, send a CSV to it from your code environment, and ask for the import. The rows land in one of your Tables, and the file never goes through the conversation.
- OAuth 2.1, registered on the fly Authorization code flow with PKCE, plus dynamic client registration, so a client can connect itself. Discovery starts at the protected-resource document.
- Everything the assistant has Your inbox, email, calendar, files, contacts, phone and texts, agents, memory and your connected apps, from one endpoint.
Connect a client
-
Sign in and connect Chrome
Create your account, then add the Chrome extension so the assistant can act in your own browser. Jobs that need no browser work without it.
-
Add the endpoint
In your MCP client, add https://sidekickpro.com/mcp over the Streamable HTTP transport. Clients that support dynamic registration need nothing else.
-
Approve the connection
You see which client is asking and what it will be able to do, then approve it. The token comes back with the scope it was granted.
-
Send a message
The client calls messageSidekick with a sentence. Watch the work happen in your browser, and the answer returns to the client.
Why route an agent through your browser
A coding agent can read your repository, but it cannot log in to the booking system, the supplier portal or the old admin page your business runs on. Those sites have no useful API, and the session that reaches them is the one in your browser.
Sidekick Pro is that session. Because its extension works inside the Chrome you already use, an agent can ask it to check a signup flow, pull last month's invoice out of a portal, or confirm that the page it just changed looks right, with your own logins and no scraped passwords.
In the web chat the work happens in a background tab and the chat shows a live view of it, so you can see what a remote client set off and take the tab over at any point. See voice browsing and Chat in Chrome for the same browser control driven by you.
What an authorized client can do
Be clear-eyed about this before you store a token. The server issues one scope, mcp:tools, and there is no narrower one. A client holding a Sidekick Pro token reaches the assistant with every tool enabled, which is the same access you have yourself: your email, your calendar, your documents, your phone number and your connected apps.
You approve each client on a consent screen that names it and says what it will be able to do, and signing out of your other devices revokes every connected client at once. Treat the token as you would your own password, and connect only clients you run yourself.
The full developer reference, including the OAuth discovery documents, the OpenAPI description and the exact tool signatures, is on the developers page.
Which clients work
Any client that speaks MCP over Streamable HTTP. Claude Code and Cursor are the common ones, and the same endpoint works from an agent framework or a script you wrote yourself. Nothing is specific to one vendor.
The other direction works too. Sidekick Pro is also an MCP client, so it can use the tools of MCP apps such as Slack, Notion and Linear in the same turn a remote agent set off.
What developers use it for
-
Checking a change in a real browser
Have your coding agent run the signup flow, the checkout or the login on a real site and report what the page actually did.
-
Sites with no API
Legacy admin pages and vendor portals that expose nothing to automate. The browser is the interface, so drive the browser.
-
Errands inside a longer job
Mid-task, an agent can have your assistant send the email, book the slot or text the customer, then carry on with its own work.
-
Loading data into Tables
A run that produces a CSV can push it straight into one of your Tables, with no chat turn and no copy and paste.
From $59/mo
Personal $59/mo · Business $149/mo
MCP Remote Control is included in Personal and Business. Business covers your whole team at one flat price, and you can cancel anytime.
Frequently asked questions
How does MCP remote control work?
Sidekick Pro runs an MCP server at https://sidekickpro.com/mcp over the Streamable HTTP transport. A connected client calls the messageSidekick tool with a plain-English message, your assistant carries it out with its own tools, and the reply goes back to the client.
Which tools does the MCP server expose?
Two. messageSidekick sends a message to your assistant and returns its reply; when a request outlives the call, the client calls it again with the checkId it got back to collect the answer. showSidekickView shows your Sidekick Pro inbox inside the chat, in apps that can show interactive views.
Can Claude Code or Cursor connect to it?
Yes. Any client that speaks MCP over Streamable HTTP can connect, Claude Code and Cursor included, as can your own scripts and agent frameworks.
How does authorization work?
OAuth 2.1: authorization code flow with PKCE and dynamic client registration, so a client can register itself. Discovery starts at the protected-resource metadata document. A signed-in Sidekick Pro session cookie also works.
What access does a connected client get?
The server issues one scope, mcp:tools, and it is all-or-nothing: the client reaches your assistant with every tool enabled, which is the same access you have. You approve each client on a consent screen that names it, and signing out of your other devices revokes every connected client.
Do I need the Chrome extension?
Only for work in your own browser. Email, calendar, documents, phone, texts and your connected apps run without it, and away from your laptop the assistant can use its private cloud browser instead.
What does it cost?
The MCP server is included in every plan, starting with Personal at $59 a month. You pick a plan when you sign in, and the Business plan covers your whole team at one flat price. Usage is billed the same way as any other request to your assistant.