Skip to main content

Overview

Minoa exposes an MCP (Model Context Protocol) server that lets any compatible AI client access your sales data — business cases, pipeline analytics, value frameworks, and more — through a standardized interface. If you’re using a platform that supports MCP, you can connect it to Minoa in minutes.
The Minoa MCP server is currently in beta. Reach out to support@minoa.io to get access.

Supported Platforms

We have step-by-step setup guides for these platforms: Using a different MCP client? The configuration below works with any client that supports the MCP protocol. See Connecting Any MCP Client for generic setup instructions.

MCP Server URL

Your Minoa MCP server URL will be provided when you’re granted beta access. Contact support@minoa.io to get your URL.

Authentication

Minoa uses OAuth 2.0 to authenticate MCP connections. The server supports:
  • Authorization Code grant type with PKCE
  • Standard OAuth discovery via /.well-known/oauth-authorization-server

How it works

  1. Your MCP client initiates an OAuth flow against the Minoa server
  2. You’re redirected to Minoa to sign in with your own account
  3. You authorize the client to access your workspace data
  4. The client receives an access token scoped to your workspace
Why personal authentication?Minoa uses per-user authentication rather than shared API keys. This means:
  • Audit trail — Every action is logged under your user, so your team knows who did what
  • Permissions — The client can only access data you’re allowed to see
  • Accountability — AI actions are tied to a real person, not an anonymous bot

OAuth Endpoints

EndpointURL
Authorization{MCP_SERVER_URL}/authorize
Token{MCP_SERVER_URL}/token
OAuth Discovery{MCP_SERVER_URL}/.well-known/oauth-authorization-server

Available Tools

Once connected, your MCP client can use the following tools:
ToolDescription
list_business_casesSearch and list business cases by name or status
get_business_caseGet full details of a specific business case
get_value_frameworkGet all use cases from your value framework library
get_value_hypothesisGet the AI-generated value hypothesis for a deal
get_pipeline_analyticsPipeline metrics, win rates, and trends
get_use_case_analyticsUse case effectiveness and win rates
create_smart_business_caseCreate a new business case with AI-recommended use cases
Your MCP client will automatically discover the full tool schemas (parameters, types, etc.) when it connects to the server.

Available Resources

MCP resources allow clients to read structured data directly from Minoa.
ResourceDescription
Value FrameworkAll active use cases with calculations and tags
Business CaseFull details including scenarios and financials
Value HypothesisAI-generated value narrative for a deal

Connecting Any MCP Client

If your MCP client isn’t listed in our platform guides, you can connect it manually using the information above. Here’s what you’ll need: Most modern MCP clients can auto-discover OAuth endpoints. Just provide:
  1. MCP Server URL — the URL provided by Minoa
  2. The client will discover authorization and token endpoints automatically via /.well-known/oauth-authorization-server

For clients requiring manual configuration

If your client doesn’t support auto-discovery, configure these settings:
SettingValue
Server URLYour Minoa MCP server URL
Authorization URL{MCP_SERVER_URL}/authorize
Token URL{MCP_SERVER_URL}/token
Grant TypeAuthorization Code
Scoperead
Auth MethodBody
If your client requires a Client ID, contact support@minoa.io to get one provisioned for your platform.

Transport

The Minoa MCP server supports Streamable HTTP transport:
  • SSE endpointGET {MCP_SERVER_URL}/ (or /sse for backwards compatibility)
  • Message endpointPOST {MCP_SERVER_URL}/ (or /messages for backwards compatibility)

Security

  • All requests are authenticated via OAuth and scoped to your Minoa workspace
  • Clients can only access data the authenticated user has permission to view
  • Access tokens can be revoked at any time by disconnecting from your MCP client
  • The server enforces rate limits to prevent abuse
  • All connections use TLS encryption

Troubleshooting

OAuth flow doesn’t start

Make sure your MCP server URL is correct and includes the full path. The server exposes discovery endpoints at /.well-known/oauth-authorization-server — if your client can’t reach these, double-check the URL.

”Missing or invalid required parameters” on token exchange

Some clients send client_id in the HTTP header instead of the request body. Set Authentication to Body in your client’s OAuth configuration.

Connection drops or times out

The MCP server supports long-lived SSE connections. If your client drops the connection, it should automatically reconnect. If issues persist, check your network/firewall settings.

Need Help?

For beta access, setup help, or any questions, reach out to support@minoa.io.