record_run_entry — bidda compliance MCP Tool
record_run_entry
(record run entry) is one of 25 tools on the
bidda compliance
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call record_run_entry from your client
- Claude Code bidda compliance record_run_entry run in your project directory
- Claude Desktop bidda compliance record_run_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bidda compliance record_run_entry ~/.cursor/mcp.json
- VS Code bidda compliance record_run_entry .vscode/mcp.json
- Zed bidda compliance record_run_entry ~/.config/zed/settings.json
- Windsurf bidda compliance record_run_entry ~/.codeium/windsurf/mcp_config.json
- Cline bidda compliance record_run_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bidda compliance record_run_entry ~/.gemini/settings.json
- Grok bidda compliance record_run_entry .mcp.json (in your project root)
- ChatGPT bidda compliance record_run_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai bidda compliance record_run_entry Settings → Connectors → Add custom connector
- LangChain bidda compliance record_run_entry pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bidda-compliance https://bidda.com/mcpOther tools on this server
- list_pillars
- search_nodes
- get_node
- get_dependency_chain
- get_crosswalk
- get_latest_changes
- get_jurisdiction_bundle
- get_mitre_mapping
- check_action_compliance
- browse_topics
- compare_jurisdictions
- create_attestation
- point_in_time
- watch_changes
- open_run
- consult_node
- get_audit_pack
- seal_run
- get_run
- drift_check
- create_control_attestation
- gap_check
- obligation_deltas
- oscal_assessment_results
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.