Connect an agent to Monomer
Connect your preferred agent through Monomer’s remote MCP server. Sign in as the Monomer user whose permissions the agent should use. You can connect before joining a Workspace. In Monomer, Your settings → Agents (select your name at the bottom of the sidebar, then Connect an agent) shows this server address for your environment, short steps for each client, and your connections.
https://api.monomer.cc/mcpYour Workspace and connector data must belong to the environment served by this URL. Follow the Workspace check below to confirm access.
Choose your client
Section titled “Choose your client”| Client | Setup guide |
|---|---|
| Claude on the web or Desktop Chat | Connect Claude |
| Claude Code CLI or Desktop Code | Connect Claude Code |
| Codex desktop app, CLI, or IDE extension | Connect Codex |
| Cursor desktop | Connect Cursor — Monomer sign-in is not yet verified |
| VS Code with GitHub Copilot | Connect VS Code — Monomer sign-in is not yet verified |
| Your own program over REST | Connect a REST client |
Use the configuration format for your client. All MCP guides use the same remote Streamable HTTP endpoint. Clients marked not yet verified accept this endpoint format, but Monomer sign-in has not been confirmed with them.
Supported clients and warehouses lists what Monomer has verified with each client.
Sign in to Monomer
Section titled “Sign in to Monomer”Monomer requires OAuth for every MCP request, including connection initialization and the tool list. Your client sends the access token with each request. A missing or invalid token returns HTTP 401 with an authorization discovery challenge; the OAuth discovery metadata remains public.
- Follow your client’s guide to add the server and start its connect or authenticate action.
- Let the client open Monomer’s authorization page in your browser. Sign in with the Google account you use for Monomer. If the page shows a different account, select Not you? Switch account to choose another Google account and return to the same request.
- Review Connect {App} to Monomer: your account, the app, and what it can do. The app acts as you, with your roles: it can ask questions and read results in the Workspaces you’re a member of, and in any you join later, and create, edit, and delete what your role allows: dashboards, pages, metrics and models, data connections, and members and invitations if you manage them. If the app is already connected to your account, the page says so; connecting again adds another connection. Select Connect {App}.
- Return to the client and enable Monomer’s tools for the conversation if required.
One connection represents one Monomer user across the Workspaces they can access. It does not combine different Google users or save a selected Organization or Workspace. Your settings → Agents lists your connections by app with when each was last used and when it expires; revoke any of them there. A connection expires 30 days after approval; reconnect from the app to keep access. Access tokens last 15 minutes and the client can refresh them during that period.
The client manages OAuth credentials. Do not put warehouse passwords, browser cookies, or copied access tokens in its configuration.
Check Workspace access
Section titled “Check Workspace access”Ask your agent:
List my Monomer Workspaces. After I choose one, list its metrics without changing anything.
The agent should call monomer_list with {"path":"workspaces"} and return the Workspaces you can access. Each result includes workspaceId, organizationId, organizationDisplayName, displayName, and sample. sample marks a Workspace with Monomer’s read-only sample data, for example {"dataset":"acme-cloud@3"}, and is null for a Workspace with your own data. Choose by Organization and Workspace name and ID; ask for clarification before making changes if names are ambiguous. The agent then calls monomer_read with {"workspaceId":"<returned-workspace-id>","path":"workspace"} and follows its availableOperations to list metrics with {"workspaceId":"<returned-workspace-id>","path":"workspace/metrics","limit":20}. Resource listings require limit as an integer from 1 to 100; there is no default. An empty metric list is valid if the selected Workspace has no metrics. For later operations with inputs, send the advertised entries to monomer_describe before constructing a call; see Direct your agent.
To discover your Organizations, call monomer_list with {"path":"organizations"}. It returns organizations with organizationId, displayName, and your current role. Both discovery calls accept only path, with no IDs, limit, or cursor. Empty results are valid when you have no memberships.
Seeing the tool list or reading public guides through monomer_docs does not establish Workspace access. Confirm the authenticated Workspace listing and the selected Workspace’s metric response before continuing.
“Without changing anything” is an instruction to the agent, not a read-only permission setting. Monomer applies your current Organization and Workspace permissions; the connection can allow changes within those permissions.
Troubleshooting
Section titled “Troubleshooting”| What you see | What to do |
|---|---|
| Sign-in expired or never returned to the client | Restart authentication from the same client and finish the new browser flow. Do not move an old consent URL to another browser. “This request expired” and “You signed in as someone else” both mean starting again from the app. |
| Tools appear, but a Workspace call asks for authentication | Use the client’s authenticate action again, then repeat the Workspace check. |
| Your Workspace is missing | Check your Google login, active membership in the Workspace’s Organization, and direct membership in that Workspace. New memberships appear without reconnecting. |
| The client asks for a Client ID or reports unsupported registration | Stop and contact Monomer. Use only the client registration details supplied by Monomer. |
| Monomer tools are missing from the conversation | Confirm the server is enabled and select its tools in the client’s conversation controls. Check your team’s connector policy if applicable. |
Monomer uses automatic OAuth client registration through Client ID Metadata Documents (CIMD). Some clients require a different registration method, so support for remote HTTP alone is not enough to complete sign-in.
If connection still fails, contact Monomer with your client name, version, and the failed step. Exclude tokens, cookies, and private Workspace data.
After the check succeeds, follow Direct your agent.