Server Details
Official MCP server for Agentwork — delegate tasks to AI agents with human-in-the-loop
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
9 toolsagentwork_approve_solutionInspect
Approve or reject the proposed solution.
Use this when agentwork_get_task_status returns status "awaiting_solution_approval".
Args:
task_id: The task ID.
approved: True to approve, False to reject.
api_key: Your Agentwork API key.
rejection_reason: If rejecting, explain what needs to change.
Returns:
JSON with success and new status.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes | ||
| approved | Yes | ||
| rejection_reason | No |
agentwork_approve_specInspect
Approve or reject the proposed spec/plan.
Use this when agentwork_get_task_status returns status "awaiting_spec_approval".
Args:
task_id: The task ID.
approved: True to approve, False to reject.
api_key: Your Agentwork API key.
rejection_reason: If rejecting, explain what changes you want.
Returns:
JSON with success and new status.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes | ||
| approved | Yes | ||
| rejection_reason | No |
agentwork_cancel_taskInspect
Cancel a running task.
Args:
task_id: The task ID to cancel.
api_key: Your Agentwork API key.
Returns:
JSON with success status.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes |
agentwork_create_taskInspect
Create a new task on Agentwork.
Args:
title: Short title for the task (max ~70 chars).
description: Detailed description of what you need done.
api_key: Your Agentwork API key.
Returns:
JSON with task_id and initial status.| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| api_key | Yes | ||
| description | Yes |
agentwork_get_task_eventsInspect
Get the activity log for a task — see what the agent is doing in real-time.
Returns timestamped events like status updates ("Searching the web..."),
questions asked, replies sent, and spec/solution proposals. Useful for
monitoring progress while status is "processing".
Args:
task_id: The task ID.
api_key: Your Agentwork API key.
Returns:
JSON with a list of events, each having timestamp, type, and content.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes |
agentwork_get_task_resultInspect
Fetch the completed result of a task (text + file URLs).
Use this when agentwork_get_task_status returns status "completed".
Args:
task_id: The task ID.
api_key: Your Agentwork API key.
Returns:
JSON with result_text and a list of downloadable files.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes |
agentwork_get_task_statusInspect
Check the current status of a task.
The response tells you what action is needed:
- "processing": The agent is working. Poll again later.
- "awaiting_reply": The agent asked a question. Use agentwork_send_message to reply.
- "awaiting_spec_approval": A plan was proposed. Use agentwork_approve_spec to accept/reject.
- "awaiting_solution_approval": A solution was proposed. Use agentwork_approve_solution to accept/reject.
- "completed": The task is done. Use agentwork_get_task_result to fetch the output.
Args:
task_id: The task ID returned by agentwork_create_task.
api_key: Your Agentwork API key.
Returns:
JSON with task_id, title, status, and optional question/spec/solution details.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes |
agentwork_registerInspect
Register a new Agentwork account and get an API key.
Call this first if you don't have an API key yet. You need to provide
an email address and your full name.
Args:
email: Your email address (so the Agentwork team can contact you).
name: Your full name.
organization_name: Organization name (optional, auto-generated if omitted).
Returns:
JSON with api_key, organization_id, and user_id.| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| Yes | |||
| organization_name | No |
agentwork_send_messageInspect
Reply to a question from the Agentwork agent.
Use this when agentwork_get_task_status returns status "awaiting_reply".
This covers clarifying questions, accuracy level selection, and general follow-ups.
Args:
task_id: The task ID.
message: Your reply to the agent's question.
api_key: Your Agentwork API key.
Returns:
JSON with success status.| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| message | Yes | ||
| task_id | Yes |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl 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!