MesiteEarly access
ContactGet started for free

Connection guide

Connect your AI to Mesite

Mesite speaks MCP, the open standard the frontier AI hosts share. One address, one sign-in with your work email, and the AI you already use can file, track, and follow up on requests for you. This page is the complete walkthrough.

Before you connect

You need three things, and only the first one usually involves anyone else:

  1. A Mesite workspace. If your company already runs Mesite, ask an admin to invite you and you will land on their board. If nobody has one yet, create one free first: a two-minute guided setup names your workspace and defines the first request your team accepts, so your AI has something real to record the moment it connects. Then come back here - sign in with the same email and the connector finds your workspace.
  2. Your work email address. That is the whole identity story: no password to create, no API key to request.
  3. An AI host that supports remote MCP connectors, on a plan that allows them. Claude, ChatGPT, and Perplexity all do, and all three keep custom connectors on their paid tiers, so a free account will not be able to add Mesite. Microsoft 365 Copilot has no custom connector option at all; we are building a Copilot agent so it works there too.
You need a Mesite workspace before the tools will answer. The connector is locked until you sign in, and every request is filed under your profile so the right person is notified when the work is done. Workspaces are born on the website - the guided signup takes about two minutes and ends with your first request type defined - and if you connect without one, the connector tells you exactly that and points you to the signup.

The connector address

Every AI host connects to the same place:

https://mesitelab.com/mcp

That single URL is all you ever paste. Behind it, your host discovers everything else it needs on its own, including where to send you for sign-in.

Connecting, host by host

Claude (web or desktop)

  1. Open Settings and go to Connectors.
  2. Choose "Add custom connector" and paste the Mesite MCP address.
  3. Claude opens the Mesite consent screen. Sign in with your work email and approve access.
  4. Start a new chat and ask for something, for example: "File a request to onboard a new vendor."

ChatGPT

  1. Open Settings and look for Connectors (on some plans this lives under Apps or developer settings).
  2. Add a new MCP server and paste the Mesite MCP address.
  3. Complete the Mesite sign-in and consent screen with your work email.
  4. Ask for what you need in a new conversation and pick Mesite when prompted.

Perplexity

  1. Open the connectors area and choose "Custom connector", then "Remote". Available on Pro, Max, and Enterprise.
  2. Paste the Mesite MCP address and choose OAuth as the authentication method.
  3. Complete the Mesite sign-in and consent screen with your work email.
  4. Custom connectors work in the Perplexity web app, desktop app, and Computer. They do not currently work in the Comet browser.

Gemini and other MCP hosts

  1. Find the MCP or connector section in the settings of your AI. Naming varies by product and moves around as these features mature.
  2. Register the Mesite MCP address as a remote server.
  3. The host discovers the rest on its own and sends you to the same Mesite sign-in and consent screen.
  4. If your host asks for a "transport", pick streamable HTTP.
  5. On Gemini, the dependable route today is Gemini Enterprise, where an administrator registers Mesite as an OAuth client with your identity provider. It is not yet a paste-the-address flow for everyone.

What happens when you connect

The first time you add the connector, your AI host registers itself with Mesite automatically and opens Mesite in your browser. If you are not already signed in, you get the same sign-in card the website uses: enter your email and click the one-click link we send, or continue with Google. No password exists at any point, and signing in once covers both your board and your AI.

The consent screen then shows exactly what your AI is asking for. When you approve, the host receives a short-lived access token and attaches it to every call it makes on your behalf. Mesite verifies that token on every single request and reads your email from it, which is how your profile is found, or created on the spot the first time.

For the technically curious: the connector is an OAuth 2.1 protected resource with dynamic client registration, published discovery metadata, and JWT verification on every call. For everyone else: paste the address, click the link in your email, approve, done.

Your first request

Just describe what you need, in your own words, in a normal chat:

  • "I need a purchase order amendment for the Accenture contract."
  • "Onboard Nordwind GmbH as a new vendor."
  • "What is the status of my request from Tuesday?"

Your AI asks Mesite what information that kind of request requires, interviews you for anything missing, and shows you a summary before anything is submitted. After you confirm, the request is recorded, routed to the right owner, and cleared through the approval rules your workspace configured: auto-approved when every requirement is met, or held for a human sign-off. You are notified when the outcome lands.

Security and trust

Approval on your terms

Your rules auto-approve a request when every requirement is met, and hold a human sign-off where you chose one. Either way, the decision is recorded.

An append-only audit trail

Every approval and status change is recorded and never overwritten, so the history of a request is always complete.

Structural tenant isolation

Your data lives inside your tenant, and every query runs through a single guarded data layer. Crossing tenants is impossible by construction.

Standards, not secrets

Access uses short-lived OAuth tokens issued to your AI after you consent. There are no API keys to copy around and no passwords stored anywhere.

Troubleshooting

My AI says the connector is unauthorized.

Your session expired or consent was revoked. Remove and re-add the connector, or use the reconnect option in your host, and complete the sign-in again.

The consent screen never opens.

Check that your host supports remote MCP servers with OAuth on your current plan, and that the address is exactly the one above, with the /mcp path included.

Mesite says my workspace cannot be found.

Your organization side is not set up yet or your email domain is not linked to a workspace. Ask your Mesite admin, since a profile only works inside an active workspace.

Requests submit but nobody picks them up.

Routing for that request type may not be configured. Your admin can review request types and routing in the admin area of the portal.

Connected and curious what your team sees on the other side?

Open the portal →