Skip to navigation
Building with AI

Taurus-PROTECT MCP server

Beta

The Taurus-PROTECT MCP server lets your AI assistant work with your Taurus-PROTECT data on your behalf: balances, wallets, transactions, requests awaiting approval, governance rules and more. It uses the Model Context Protocol (MCP) over HTTPS, so any compatible assistant connects to it with nothing to install. You sign in once, in your browser, with your own Taurus-PROTECT account and approve what the assistant may do. From then on, it works with your permissions, and nothing more.

How it works

MCP over HTTPS your own session sign-in and consent, once You AI assistantClaude, Claude Code, ... Taurus-PROTECTMCP server Taurus-PROTECTbackend Taurus-PROTECTsign-in page

Server details

ItemValue
Server URLProvided by your Taurus-PROTECT administrator, for example https://mcp.example.com/mcp
TransportStreamable HTTP (remote MCP server)
AuthenticationOAuth 2.1 with PKCE: your usual Taurus-PROTECT sign-in, then a consent screen listing what the assistant may do
AccessYour own Taurus-PROTECT permissions and tenant, limited to the capabilities you approve
Default modeRead-only. Write tools appear only when your administrator enables them

Before you begin

  • A Taurus-PROTECT user account, on a tenant where your organization has enabled the MCP server.
  • The server URL, from your Taurus-PROTECT administrator.
  • An AI client that supports remote MCP servers with OAuth sign-in.
  • A browser on the same computer as the client, to sign in.
What you can do

What the assistant can look up and run.

Connecting

Claude, Claude Code and other MCP clients.

Security and limits

Rules the server enforces, whatever is asked.

Administrators: setup and configuration are covered in the operator guide, available to clients on request.