API To MCP Tool Conversion

Connected APIs turn a normal authenticated HTTP endpoint into a private AgentPMT tool that your MCP-connected agent can call. You define the allowed URLs, HTTP methods, credentials, and agent-facing instructions in the dashboard. AgentPMT then exposes a tool named API Access <name> with safe actions for the agent.

The value is the boundary: the agent can send a request, but it never sees API keys, bearer tokens, OAuth tokens, passwords, cookies, or authorization headers. AgentPMT checks the request against your endpoint profile, injects credentials server-side, charges the Agent Group for the allowed API call, and records the activity.

What You Will Need

• An AgentPMT account with at least one Agent Group
• An API endpoint reachable from AgentPMT over HTTP or HTTPS
• The credential the upstream API expects: an API key, a bearer token, or a Basic Auth username and password
• A short description of when the agent should use this API

What Gets Created

Step 1 - Create the Connected API

Open Dashboard -> Connected APIs and click Add New. This opens the builder for a credential-injection API tool.

Step 2 - Define the Endpoint Boundary

Add one or more approved base URLs. The agent can call a relative path under an approved base URL, or an approved absolute URL, but it cannot forward requests to arbitrary hosts.

Relative paths resolve only when the tool has exactly one approved base URL. If you approve two or more base URLs, the agent must send an approved absolute URL in endpoint instead of a relative path.

Use the narrowest URL that still covers the task:

Step 3 - Bind Authentication

Choose how the upstream API expects authentication, then bind the credential value. The agent should not know the raw secret or the exact authorization header.

The builder offers three auth types:

• API key injected into a header, query parameter, or body field. For an API with a non-standard auth header, choose the API key type and set the header name (and target) yourself.
• Bearer token injected into the Authorization header as Bearer <token>.
• Basic Auth from a username and password, injected into the Authorization header as Basic <base64(username:password)>.

When the builder saves, AgentPMT creates the private tool, stores the endpoint profile, and scopes the credential binding to that tool.

Step 4 - Make It Available to an Agent Group

The Connected API exists as a private tool. Your MCP client only sees it when the Agent Group behind its Bearer token is allowed to use private tools or has the specific tool authorized.

Step 5 - Call It From an MCP Agent

Connect your MCP client to AgentPMT using the Agent Group Bearer token from Connection. After the client refreshes tools, the Connected API appears as a private tool with these actions:

Ask the agent to use the API in task language:

Use API Access Acme CRM to fetch customer 123 and summarize open tickets.

A typical send_request call looks like this:

{
  "action": "send_request",
  "method": "GET",
  "endpoint": "/v1/customers/123/tickets",
  "query": {},
  "headers": {
    "Accept": "application/json"
  },
  "body": {}
}

Do not include Authorization, API keys, bearer tokens, cookies, or OAuth values in the tool input. If the request matches the endpoint profile, AgentPMT injects the configured credential and forwards the request.

Runtime Guardrails

• The request method must be in the allowlist you chose in the builder.
• The destination must match one of the approved base URLs.
• A relative endpoint resolves only when the tool has a single approved base URL; with multiple base URLs the agent must send an approved absolute URL.
• Agent-supplied auth and transport headers (Authorization, Cookie, Host, and similar) are stripped before the request is sent, then the configured credential is injected.
• Auth values are injected server-side and are not returned to the agent.
• Credential bindings use product-only scope for the Connected API.
• Agent Group controls still apply: disabled tools, inactive endpoints, frozen spend, missing credits, or missing private-tool access prevent use.
• Deactivating the Connected API in the dashboard stops future calls without deleting the saved configuration.

Troubleshooting

Related Docs