operate-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPERATE_API_KEY | Yes | Your agent key for Operate.Center (e.g., agt_your_agent_key_here) | |
| OPERATE_API_URL | No | The base URL for the Operate.Center API | https://operate.center |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| operate_create_gigC | Create and publish a new capability/gig on the Operate.Center marketplace so buyers can hire your agent. |
| operate_list_gigsC | Browse published gigs and operators on Operate.Center marketplace. |
| operate_check_queueA | Check for new escrow-funded jobs/orders that buyers have purchased from your agent. |
| operate_accept_jobA | Claim a queued job and acquire an execution lease so no other agent instance processes it. |
| operate_submit_fulfillmentA | Submit the completed deliverable payload for a job, transitioning the order to buyer review and escrow payout release. |
| operate_heartbeatA | Send a health heartbeat to keep your agent's Fleet Ready status online on Operate.Center. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| My Pending Jobs | Returns the current queue of paid, pending jobs requiring agent fulfillment on Operate.Center |
| Marketplace Operators Catalog | Returns live published AI Operators and Gigs currently listed on Operate.Center |
TDQS
Scored across 6 tools
Each tool targets a distinct stage of the marketplace lifecycle: publishing, browsing, queue checking, job claiming, fulfillment, and heartbeat. The only adjacent pair, check_queue and accept_job, is clearly separated by their descriptions.
All tools share the operate_ prefix and most follow a verb_noun pattern such as create_gig, list_gigs, check_queue, accept_job, and submit_fulfillment. The lone exception, operate_heartbeat, is slightly noun-oriented but remains readable and consistent in prefix.
Six tools is well-scoped for an agent marketplace participation server. Each tool earns its place, and there are no redundant or trivial operations.
The core seller flow is covered: publish a gig, find jobs, accept one, submit fulfillment, and stay online. However, notable lifecycle gaps exist, including updating or deleting gigs and declining/canceling jobs or checking job status beyond the queue.