Skip to content

Commit aeea95a

Browse files
authored
Merge branch 'main' into reshuffle-ai-section
2 parents 8d1fe5c + 327e143 commit aeea95a

2 files changed

Lines changed: 37 additions & 2 deletions

File tree

ai/mcp-server/setup.mdx

Lines changed: 36 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,11 @@ The public Checkly MCP Server currently supports these clients:
2525
| Claude Code | Supported | Add the server with the HTTP transport. |
2626
| Devin CLI | Supported | Requires Devin CLI and uses Checkly's static Devin MCP OAuth client. |
2727
| Antigravity | Supported | Use the Checkly MCP endpoint as the MCP server URL. |
28+
| OpenCode | Supported | Uses Checkly's static OpenCode MCP OAuth client with OpenCode's default redirect URI. |
2829
| Cursor | Supported | Uses Checkly's static Cursor MCP OAuth client. Configure `.cursor/mcp.json` or `~/.cursor/mcp.json`. |
2930
| VS Code | Supported | Configure `.vscode/mcp.json` or your VS Code user profile. |
3031

31-
Supported clients must use a Checkly-approved OAuth client in Auth0. Most supported clients use [OAuth Client ID Metadata Documents (CIMD)](https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/). Cursor and Devin CLI use Checkly's static MCP OAuth clients. Clients that rely on DCR are not supported.
32+
Supported clients must use a Checkly-approved OAuth client in Auth0. Most supported clients use [OAuth Client ID Metadata Documents (CIMD)](https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/). Cursor, Devin CLI, and OpenCode use Checkly's static MCP OAuth clients. Clients that rely on DCR are not supported.
3233

3334
If you want Checkly to support another compatible client, [share feedback or requests](https://feedback.checklyhq.com).
3435

@@ -76,6 +77,40 @@ Complete the OAuth flow when prompted.
7677

7778
Follow Google's [Antigravity MCP integration](https://antigravity.google/docs/mcp) guide. Use the Checkly MCP endpoint from this page as the MCP server URL.
7879

80+
## OpenCode
81+
82+
<Accordion title="Before you begin">
83+
Before configuring OpenCode, ensure you have:
84+
85+
- OpenCode installed
86+
- Port `19876` available for the OAuth callback
87+
</Accordion>
88+
89+
Add the server to your OpenCode configuration:
90+
91+
```json opencode.json
92+
{
93+
"mcp": {
94+
"checkly": {
95+
"type": "remote",
96+
"url": "https://api.checklyhq.com/mcp",
97+
"oauth": {
98+
"clientId": "tpc_q3CQpmc7tU8LGwAbTLwDR6",
99+
"redirectUri": "http://127.0.0.1:19876/mcp/oauth/callback"
100+
}
101+
}
102+
}
103+
}
104+
```
105+
106+
Then authenticate:
107+
108+
```bash Terminal
109+
opencode mcp auth checkly
110+
```
111+
112+
OpenCode must use the redirect URI shown above. If port `19876` is already in use, this static OAuth client will not work with a different local callback port unless Checkly has approved that redirect URI.
113+
79114
## Cursor
80115

81116
Add the server to `.cursor/mcp.json` in your project, or to `~/.cursor/mcp.json` for all projects:

platform/private-locations/overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ new ApiCheck('hello-api-1', {
8484

8585
## Unavailable Private Locations
8686

87-
If a private location has checks assigned but no Checkly agents connected for more than 20 minutes, it will be flagged as unavailable. Checkly will email account owners and admins when this happens.
87+
If a private location has checks assigned but no Checkly agents connected in the last 10 to 20 minutes, it will be flagged as unavailable. Checkly will email account owners and admins when this happens.
8888

8989
While a location is unavailable, no checks will be scheduled to run on it. When a location becomes available, check scheduling and execution will resume automatically.
9090

0 commit comments

Comments
 (0)