AI Agent Access (MCP)
AI Agent Access lets AI assistants work with your New Instance data safely. The Model Context Protocol (MCP) is the open standard AI tools use to call external systems - Claude Desktop/Code, IDE agents and agent frameworks all speak it. Point any of them at this endpoint with your API key and they can list your BugWatch projects, browse issues, and run the platform's AI root-cause analysis - scoped to exactly what the key allows, with your organisation boundary enforced server-side.
One endpoint, stateless JSON-RPC 2.0:
POST https://service.newinstance.cloud/mcp
x-api-key: sk_live_KEYID:secret (or Authorization: Bearer KEYID:secret)
Content-Type: application/json
Accept: application/json, text/event-stream
- Server keys only. Publishable widget keys (bare key ID) are rejected with
401/ JSON-RPC-32001. - Org scoping is automatic - every tool runs against the org that owns the key; there is no way to pass another org.
- Scope-filtered tools - a key sees only tools for products in its scopes (
FULL_ACCESSsees all). - Stateless - each POST is independent; no session handshake is required (send
initializeonly if your client library insists). GET/DELETE return405. - Responses stream back as a single SSE frame (
data: {…}); parse thedata:line as JSON.
Current tools (BugWatch): bugwatch_list_projects, bugwatch_list_issues, bugwatch_root_cause_analysis.
Claude Desktop config example:
{ "mcpServers": { "newinstance": {
"url": "https://service.newinstance.cloud/mcp",
"headers": { "x-api-key": "sk_live_KEYID:secret" } } } }/mcpList available tools
List the tools this key can use. Keys scoped to BugWatch (or FULL_ACCESS) see the three BugWatch tools; a key with no matching product scopes sees an empty list.
Response - result.tools[] with name, description and a JSON-Schema inputSchema per tool.
Headers
x-api-keyAcceptRequest body
application/json{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Responses
401 – Not a server key
{
"jsonrpc": "2.0",
"error": {
"code": -32001,
"message": "Unauthorized: this endpoint requires a server API key (keyId:secret) in the x-api-key header or as a Bearer token."
},
"id": null
}https://api.newinstance.cloud/mcpHeaders
x-api-keyAcceptRequest body
Code samples
curl -X POST 'https://api.newinstance.cloud/mcp' \
-H 'Content-Type: application/json' \
--data-raw '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}'