Model Context Protocol

Your assistant, connected to Prevalentware IDP

Discover platform APIs and use them from your assistant with your account and permissions. Connect once and authorize access in your browser.

Streamable HTTPOAuth 2.1 · PKCE2 tools · platform API
MCP URL
https://server.ai.prevalentware.com/mcp

Server: prevalentware-idp-mcp. This URL points to the API for this environment.

1. Configure your client

Choose your assistant and add the configuration. If the file already exists, keep its options and other servers.

Terminal, from your project

Run the command. Then open Claude Code, enter /mcp and select the server to authenticate.

Claude Code configuration
claude mcp add --transport http prevalentware-idp-mcp https://server.ai.prevalentware.com/mcp

Claude Code documentation

2. Authorize with your account

  1. Start the connection in your client. The browser will open the Prevalentware IDP sign-in page.
  2. Use the same account you use on the platform. If you are already signed in in that browser, you can continue with that session.
  3. Review the client and requested permissions, then authorize the connection. Return to your assistant when finished.

Authorization preserves your permissions and customer scope on the platform. You do not need to paste tokens, cookies or passwords into the configuration file.

3. Discover before executing

The catalog comes from the current backend OpenAPI contract. You do not need to guess routes or parameters: find an API and review its complete contract.

prevalentware_idp_api_discover
Search by text and method; paginate with offset and limit. With method and path, it returns parameters, bodies, responses and related schemas. The catalog describes the API; permissions are checked during execution.
prevalentware_idp_api_execute
Execute a discovered operation with your identity. Use the route template and pathParams for identifiers. Writes change real data and require your authorization.
First query for your assistant
Use prevalentware-idp-mcp to discover the document APIs. Review the contract for a GET operation and explain its parameters. Do not execute operations that modify data.

To check the connection, find both tools and start with discovery. Then request a GET query using the contract parameters. Large responses require pagination or a narrower query.

If the connection does not complete

The server is missing: check the file, open the project where you saved it and reload its MCP connections. Some clients separate global and project configuration.

Authentication pending or 401: start authorization from the client. Opening the MCP URL in a browser without authorization may return 401; that URL is a protocol endpoint.

403 during execution: your account does not have permission for that operation. An MCP connection does not expand platform permissions.

Client with a remote callback: its return domain must be approved by an administrator. Desktop clients can use local callbacks; a cloud-hosted connector may need additional configuration.

Automatic discovery

Clients supporting Streamable HTTP and OAuth discover the authorization server, scopes and client registration from public metadata.

View MCP OAuth metadata