# NEXUS AI MCP

NEXUS AI has an existing MCP service with 74 operational tools. This agent site does not implement a second MCP server.

## Endpoint

```text
https://mcp.nexusai.run/mcp
```

Connect clients directly to that URL. The discovery route [`/mcp`](/mcp) on this site returns endpoint metadata, and MCP requests sent to it are redirected (HTTP 308) to the endpoint above; this site does not proxy MCP traffic. The server card is at [`/.well-known/mcp.json`](/.well-known/mcp.json).

The public [MCP tool catalog](/mcp/tools.json) lists the verified tool names, required scopes, risk classification, and safety policy without exposing operational data.

## Authentication

The MCP service uses OAuth 2.0 with PKCE and dynamic client registration. Interactive clients sign in through a browser; headless clients run the same flow once and send the access token as a Bearer token. Personal access tokens (`nxk_`) are for the REST API, not MCP. OAuth metadata: `https://mcp.nexusai.run/.well-known/oauth-protected-resource` and `https://mcp.nexusai.run/.well-known/oauth-authorization-server`. Setup steps for each client are in the [Quick start](/docs/quickstart.md).

## Tool policy

Available tools are determined by the deployed MCP server and the caller's permissions. Do not infer tool availability from a tool name alone, and do not grant destructive permissions by default.

The current tool families are identity and discovery, AI Builder, deployments, secrets, custom domains, external database intelligence, deployment databases and backups, persistent volumes, S3-compatible buckets, managed databases, and support tickets.

## Related resources

- [API](/docs/api.md)
- [Security](/docs/security.md)
- [NEXUS MCP endpoint](https://mcp.nexusai.run/mcp)