Server Details
AgentPMT is the AI agent marketplace that turns any MCP-compatible AI assistant into an autonomous employee. Connect once and your agents gain access to a growing ecosystem of tools, workflows, and skills spanning communication, data analytics, development, file management, search, and more. AgentPMT dynamically discovers and orchestrates tools from across the MCP ecosystem, so your agents can independently find the right tool for any task without manual configuration.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
4 toolsAgentPMT-Report-Tool-IssueTry in Inspector
Report an issue with a tool to the AgentPMT team.
| Name | Required | Description | Default |
|---|---|---|---|
| tool_name | Yes | ||
| error_message | Yes | ||
| recommended_improvements | No |
AgentPMT-Send-Human-RequestTry in Inspector
AgentPMT Send Human Request - Send a request to your human to enable a tool, workflow, or add funds to your budget.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Product/workflow ObjectId for access requests, or optional target identifier for check_response lookup | |
| action | No | Operation to perform: send (default) or check_response. | send |
| request | No | Freeform request body to send to the user (required when action=send) | |
| request_id | No | Mobile approval request ObjectId to check when action=check_response. | |
| request_type | No | Request type: add_funds, enable_tool, enable_workflow, notification_only, other (required when action=send). Use notification_only to send a message that does not require approval. | |
| include_request | No | When action=check_response, include the full request record in the response. |
AgentPMT-Tool-Search-and-ExecutionTry in Inspector
AgentPMT Tool Search and Execution - Unified interface for discovering, searching, and using AgentPMT tools without MCP refresh. Access tools required for workflows and skills here.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (1-based). Used when listing tools. | |
| query | No | Search query for text and semantic matching. If provided, performs hybrid search. | |
| action | Yes | Operation to perform: get_tools (discover tools - list/search/workflow), get_schema (full tool schema by ID), request_credentials (email user to add credentials), call_tool (execute a tool), get_instructions (help) | |
| message | No | Custom message to include in credential request notification (for request_credentials action) | |
| tool_id | No | Tool/product ID (required for get_schema and use actions) | |
| page_size | No | Number of results per page (1-100) | |
| tool_name | No | Alternative: Tool name to search for (for use action, searches then executes first match) | |
| parameters | No | Parameters to pass to the tool when using 'use' action | |
| workflow_id | No | Workflow/skill chain ID. If provided, returns all tools from that workflow. |
AgentPMT-Workflow-SkillsTry in Inspector
AgentPMT Workflow Skills - Fetch, Search, and Use Agent Workflows and Skills. Use to retrieve, initiate, and complete workflows.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | Number of results to skip for pagination | |
| limit | No | Maximum results to return (1-200) | |
| query | No | Optional substring search over name/description (case-insensitive) | |
| action | Yes | Operation to perform: search, get_workflow_skill, start_workflow, end_workflow, get_active_workflow, get_instructions | |
| rating | No | Workflow rating from 1-5 stars (required for end_workflow) | |
| comment | No | Comment about the workflow experience (required for end_workflow) | |
| skill_id | No | Skill chain ObjectId or slug (required for get_workflow_skill, start_workflow, end_workflow) | |
| publisher | No | Filter by publisher username (case-insensitive substring match) | |
| categories | No | Comma-separated category names to filter by | |
| industry_tags | No | Comma-separated industry tag names to filter by | |
| suggested_improvements | No | Suggested improvements or changes to the workflow (optional) |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!