Connect and verify an MCP server This walkthrough connects the hosted Sentry MCP endpoint and verifies access without changing an issue. You will finish with a saved connection, an inspected tool catalog, and a read-only result that you can compare against the Sentry web interface. Prerequisites - A working agent session with a configured model provider. - A Sentry account with access to an organization and project you are authorized to inspect. - A browser for authorization and network access to https://mcp.sentry.dev/mcp. This uses an external service. Its available tools and account requirements can change. Connecting it does not give the agent permissions beyond the account and scopes you authorize. Do not use a production administrator account merely to make the example work. 1. Inspect existing connections agent-cli mcp list Look for an existing Sentry entry before adding another. If the label sentry is already in use, inspect that connection in /mcp; do not overwrite it blindly. The command lists configured servers without printing environment values. 2. Add the hosted endpoint If no corresponding connection exists, run: agent-cli mcp add sentry --transport http https://mcp.sentry.dev/mcp agent-cli mcp list The second command should now list sentry. This verifies that configuration was saved, not that authorization succeeded. The entry lives in ~/.haskell-agent/config.json. Alternatively, open /mcp in the agent, press a, and enter the same URL. The interactive add flow starts OAuth when required and restarts the MCP runtime after a saved change. 3. Authorize the intended account - Open an interactive agent session and enter /mcp. - If the session was running when you changed configuration externally, press r to restart its MCP runtime. - Select the Sentry connection with the arrow keys. Press i to authorize or re-authorize the HTTP server. - Check the service, signed-in account, organization access, and requested scopes in the browser. Grant only access you intend the agent to use. - Return to the agent and inspect the connection state. If you cancel authorization, the saved connection can remain present but unusable. A listed server is not proof of a valid grant. Never paste an OAuth callback URL or token into a public issue report. 4. Inspect the actual tool catalog With Sentry selected in /mcp, press Enter to inspect its tools. Choose an operation whose description explicitly reads or lists data. Do not assume that a remembered tool name still exists: the service can update its catalog. In deferred-discovery sessions, a connected tool may not yet be visible to the model. Request discovery explicitly: Discover the Sentry tools that can list the organizations or projects accessible to my account. Do not perform any mutation. Expected result: discovery of relevant tools from the Sentry connection, not a generic explanation of the Sentry API. If no tool appears, return to the manager and check the connection before retrying the prompt. 5. Verify a read-only result Use the connected Sentry server to list the organizations or projects I can access. Report their identifiers and names. Do not create, update, resolve, assign, or delete anything. Inspect the tool call and its result. If an approval is requested, read its operation and arguments; cancel if it performs a mutation. A server's read-only annotation is a declaration by that server, not an independent guarantee. - Confirm the result came from the Sentry connection. - Open the Sentry web interface yourself and compare an organization or project identifier. - If the result is empty, verify that the authorized account has access before treating it as a connection failure. You now have stronger evidence than “connected”: the configured account can perform an authorized read and return recognizable data. 6. Investigate one issue without changing it Choose an issue you are permitted to read and substitute its actual identifier: Read Sentry issue PROJECT-123 using the connected server. Summarize its error, affected release, and available stack-trace evidence. Do not resolve, assign, comment on, or otherwise modify it. Tell me if a requested field is unavailable. Compare the returned evidence against the issue page. Treat a proposed code fix as a hypothesis until it is checked against the repository and reproduced in a test. An MCP connection supplies external context; it does not prove the cause of an application bug. Recover from failures Failure | Next action | Entry missing in a running session | Verify agent-cli mcp list, then /mcp and r to reload the catalog | HTTP 401 or expired grant | Re-authorize the selected HTTP server with i and verify the browser account | HTTP 403 or missing organization | Check Sentry account membership and requested scopes; do not broaden access without understanding the missing permission | Connected but expected tool absent | Inspect the live catalog and repeat discovery; do not invent a tool name | Read times out | Check service/network health and try a smaller read once; retain the error for diagnosis | Mutation outcome uncertain | Inspect the remote issue state before any retry; a timeout does not mean the operation did not execute | Disable or remove the connection agent-cli mcp disable sentry Restart the running MCP runtime with /mcp, then r, to pick up the external edit. To remove the saved entry interactively, select it and press x, then y. Disabling or removing a local connection is not the same as revoking the service-side OAuth grant; revoke that through Sentry's account controls when access is no longer wanted. Continue with the MCP integration reference for local stdio servers, complete configuration fields, protocol selection, resources, prompts, and optional client capabilities.