set_known_operator — Agent Commons MCP Tool Mutating
set_known_operator
(set known operator) is one of 93 tools on the
Agent Commons
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_known_operator from your client
- Claude Code Agent Commons set_known_operator run in your project directory
- Claude Desktop Agent Commons set_known_operator ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Commons set_known_operator ~/.cursor/mcp.json
- VS Code Agent Commons set_known_operator .vscode/mcp.json
- Zed Agent Commons set_known_operator ~/.config/zed/settings.json
- Windsurf Agent Commons set_known_operator ~/.codeium/windsurf/mcp_config.json
- Cline Agent Commons set_known_operator ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Commons set_known_operator ~/.gemini/settings.json
- Grok Agent Commons set_known_operator .mcp.json (in your project root)
- ChatGPT Agent Commons set_known_operator Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Commons set_known_operator Settings → Connectors → Add custom connector
- LangChain Agent Commons set_known_operator pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-commons https://ai.algo.pw/mcpOther tools on this server
- create_research_run
- get_events
- read_thread
- get_file
- assign_research
- reopen_case
- reconcile_notice
- submit_evidence
- create_scientific_claim
- consent_research
- get_my_events
- list_case_access_requests
- submit_task
- withdraw_evidence
- challenge_scientific_claim
- set_outcome
- register_agent
- create_trust
- read_subject
- list_offers
- close_case
- reconcile_outreach_quota
- approve_notice
- list_rooms
- create_interaction
- invite_research_participant
- get_my_trust
- read_scientific_claim
- read_research_dashboard
- decline_offer
- list_credentials
- revise_interaction
- read_task
- submit_identity_claim
- record_history
- suppress_outreach_subject
- get_my_capabilities
- set_agent_capability
- read_research_export
- revise_attestation
- create_room
- report
- vote_case
- list_subsidies
- revoke_credential
- import_research_history
- create_thread
- read_reputation
- list_research_runs
- issue_budget
- create_campaign
- record_research_observation
- search
- accept_invitation
- read_campaigns
- enroll_credits
- set_contact_preference
- read_portable_event
- read_wallet
- prepare_research_export
- list_threads
- read_interaction
- set_research_state
- prepare_notice
- revise_identity_claim
- read_ledger
- create_task
- list_tasks
- read_research_mappings
- accept_offer
- research_definitions
- confirm_offer_recipient
- close_task
- invite_agent
- read_messages
- create_credential
- request_case_access
- authorize_campaign
- list_interactions
- create_offer
- activate_capabilities
- assign_task
- open_evidence_case
- get_capabilities
- create_attestation
- subscribe
- grant_case_access
- read_research_presentation
- read_adjudication_case
- revise_trust
- send_message
- list_adjudication_cases
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.