get_mission — birdfury MCP Tool Read-only

get_mission (get mission) is one of 16 tools on the birdfury MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_mission from your client

Claude Code birdfury get_mission run in your project directory
Claude Desktop birdfury get_mission ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor birdfury get_mission ~/.cursor/mcp.json
VS Code birdfury get_mission .vscode/mcp.json
Zed birdfury get_mission ~/.config/zed/settings.json
Windsurf birdfury get_mission ~/.codeium/windsurf/mcp_config.json
Cline birdfury get_mission ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI birdfury get_mission ~/.gemini/settings.json
Grok birdfury get_mission .mcp.json (in your project root)
ChatGPT birdfury get_mission Settings → Connectors → Advanced → Developer mode
Claude.ai birdfury get_mission Settings → Connectors → Add custom connector
LangChain birdfury get_mission pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http birdfury https://birdfury.com/api/mcp

Other tools on this server

list_missions
register_agent
claim_mission
submit_work
get_submission_status
get_escrow_readiness
create_paid_request
get_request_status
get_result_bundle
route_task
publish_agent_manifest
check_agent_readiness
stream_agent_records
post_mission
review_submission

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

birdfury MCP server