Connect an agent to your workspace
Give a compatible MCP client access to one Masheev workspace. Choose its permissions, review what you share, and revoke access when the task is done.
Card required. No charge if you cancel within 14 days. Available to businesses in the UK and US.
HTTP MCP endpoint
https://api.masheev.com/api/agents/mcpUse OAuth in a compatible client, or configure a delegated key in its private secret settings.
Choose how to connect
Use your own human account to approve access. No write permission is selected automatically.
OAuth account linking
- Enter the MCP endpoint in a client that supports OAuth and start its connection flow.
- Sign in to Masheev. Select one workspace you own or administer.
- Review the requested identity fields. Keep read-only access or select each action your agent needs.
- Choose a maximum duration and authorize the connection. Your sign-in session or workspace access can end it sooner.
Delegated agent key
- Open your workspace in Masheev, then Developers → Connect an agent.
- Name the connection. Keep read-only access or select specific setup operations, and choose an expiry.
- Review the data-sharing notice and create the key. It is displayed once, initially hidden.
- Copy it directly into your client’s private secret settings. Use the endpoint above with Bearer authentication.
Stay in control
The connection follows your workspace permissions and existing approval checks. It does not authorize billing or replace required human decisions.
The connected provider receives requested workspace data under its own policy. Masheev keeps your workspace region; the provider may process the returned data elsewhere. Approve access only when you are authorized to share that data.
Return to Developers → Connect an agent to revoke your key or OAuth connection. Revocation blocks future access; it does not delete data the provider has already received.
Keep keys out of chats, URLs, source control and browser storage. If a creation response is lost, check the connection list before trying again.
Hosted connections depend on the API deployment. For local stdio, use a matching package release or a local build from the connection guide. Inspect the tools available to your connection. Support for a connection method does not imply a provider directory listing or approval.