Nexra
Start in the sandbox

Build · MCP gateway

One MCP endpoint. Every action governed.

Agents reach Nexra over the Model Context Protocol. Each credential sees only the tools published on its server, and every write goes through the same policies, approvals and evidence as the console.

Set up a serverRead the MCP guide
Streamable HTTP · POST
POST https://api.nexra.amakoragroup.com/mcp
Authorization: Bearer <access token>
MCP-Protocol-Version: 2025-11-25

How a client connects

  1. 01

    Add the server URL

    Clients that support MCP authorisation need nothing else. Nexra answers with its OAuth metadata.

  2. 02

    Sign in and approve the client

    You see the client’s name and where it will return you, then choose the application and MCP server it may use.

  3. 03

    Call the published tools

    The credential decides which tools are visible. Tokens last an hour; refresh tokens rotate on every use.

  4. 04

    Revoke at any time

    Each approval creates a named credential on the application. Revoke it and the client is disconnected immediately.

What an agent can call

Three tools for business systems, alongside the catalogue, docs and run tools you publish on the server.

search_capabilitiesconnect:read
Find actions on the connections in the application’s project. Writes you have not switched on never appear.
describe_capabilityconnect:read
Read an action’s inputs, risk tier and the policy decision it would get, before calling it.
execute_capabilityconnect:execute
Run the action through the governance gate. It may run, wait for approval or be refused, and each outcome is recorded.

Clients

  • Claude, ChatGPT, Cursor, VS CodeOAuth sign-in with the server URL
  • Microsoft Copilot StudioGuided setup through the Copilot Studio MCP wizard
  • Your own agentClient credentials, exchanged for a one-hour token