Paperclip AI Adapter for Antigravity CLI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAPERCLIP_ORG_ID | No | Your organization ID | |
| PAPERCLIP_API_KEY | Yes | Your Paperclip API key | |
| PAPERCLIP_API_URL | No | API base URL | https://localhost:3100 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paperclip_list_agentsB | List all AI agents in the Paperclip organization with their roles and status |
| paperclip_create_agentA | Create a new AI agent (hire) in the Paperclip organization with a specific role |
| paperclip_get_agentA | Get details of a specific Paperclip AI agent including status, role, and budget |
| paperclip_update_agentC | Update an existing Paperclip AI agent configuration |
| paperclip_delete_agentB | Delete (terminate) a Paperclip AI agent |
| paperclip_wake_agentA | Wake/trigger an agent to start working on its assigned issues |
| paperclip_pause_agentA | Pause an agent, stopping it from picking up new work |
| paperclip_set_agent_budgetB | Set spending budget limit for an agent |
| paperclip_list_issuesA | List all issues/tasks on the Paperclip Kanban board with optional filters |
| paperclip_create_issueC | Create a new issue/task on the Paperclip Kanban board |
| paperclip_get_issueA | Get details of a specific issue including cost summary |
| paperclip_update_issueB | Update an existing issue (title, status, priority, assignee, etc.) |
| paperclip_delete_issueB | Delete an issue from the Kanban board |
| paperclip_checkout_issueA | Atomically claim/checkout an issue so no other agent can work on it |
| paperclip_release_issueA | Release a previously checked-out issue so other agents can claim it |
| paperclip_list_commentsA | List comments on a specific issue |
| paperclip_add_commentC | Add a comment to an issue |
| paperclip_get_issue_costB | Get cost summary for a specific issue (tokens used, total cost) |
| paperclip_list_projectsA | List all projects in the Paperclip organization |
| paperclip_create_projectA | Create a new project to organize issues and goals |
| paperclip_get_projectB | Get details of a specific project |
| paperclip_list_goalsB | List all goals (Company → Project → Agent → Task hierarchy) |
| paperclip_create_goalB | Create a new goal in the hierarchy (company, project, or agent level) |
| paperclip_get_goalA | Get details of a specific goal |
| paperclip_list_approvalsB | List all pending and resolved approval requests |
| paperclip_create_approvalB | Create a new approval request for governance gate |
| paperclip_approval_decisionA | Approve or reject a pending approval request |
| paperclip_get_companyA | Get details of the Paperclip company/organization (agent count, project count, etc.) |
| paperclip_whoamiA | Get identity information about the current authenticated user/agent |
| paperclip_api_requestB | Make a raw API request to any Paperclip endpoint (escape hatch) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
Most tools pair a clear verb with a unique resource and action, so an agent can usually pick correctly. The main ambiguity is paperclip_get_issue_cost overlapping with paperclip_get_issue, which already includes cost summary, and paperclip_api_request duplicating the whole surface as an escape hatch.
The paperclip_ prefix and snake_case verb_noun pattern are applied consistently across nearly all tools. Minor exceptions are paperclip_approval_decision, paperclip_whoami, and paperclip_api_request, which do not follow the standard verb_noun convention.
At 30 tools, this exceeds the 25+ threshold and feels heavy for an MCP adapter. Although the tools are organized by domain, some are redundant or could be consolidated, such as paperclip_get_issue_cost overlapping with paperclip_get_issue.
Agents and issues have full CRUD plus useful lifecycle actions, but projects and goals only support create/get/list with no update or delete, and comments lack update/delete. These are notable gaps, though paperclip_api_request provides a raw workaround.