check_schedule_conflicts — agendaforge MCP Tool Read-only
check_schedule_conflicts
(check schedule conflicts) is one of 55 tools on the
agendaforge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_schedule_conflicts from your client
- Claude Code agendaforge check_schedule_conflicts run in your project directory
- Claude Desktop agendaforge check_schedule_conflicts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agendaforge check_schedule_conflicts ~/.cursor/mcp.json
- VS Code agendaforge check_schedule_conflicts .vscode/mcp.json
- Zed agendaforge check_schedule_conflicts ~/.config/zed/settings.json
- Windsurf agendaforge check_schedule_conflicts ~/.codeium/windsurf/mcp_config.json
- Cline agendaforge check_schedule_conflicts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agendaforge check_schedule_conflicts ~/.gemini/settings.json
- Grok agendaforge check_schedule_conflicts .mcp.json (in your project root)
- ChatGPT agendaforge check_schedule_conflicts Settings → Connectors → Advanced → Developer mode
- Claude.ai agendaforge check_schedule_conflicts Settings → Connectors → Add custom connector
- LangChain agendaforge check_schedule_conflicts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agendaforge https://mcp.agendaforge.app/mcpOther tools on this server
- list_my_orgs
- list_events
- get_event
- list_sessions
- get_session
- get_agenda
- list_forms
- list_submissions
- list_speaker_tasks
- search
- semantic_search
- list_tracks_rooms
- list_speakers
- list_sponsors
- get_contact
- list_associated_contacts
- search_contacts
- get_review_progress
- get_registration_stats
- list_attendees
- get_email_activity
- list_email_templates
- draft_email
- list_pending_approvals
- import_contacts
- add_contact_note
- send_speaker_reminder
- send_speaker_message
- update_session
- delete_session
- remove_session_speaker
- create_sponsor
- update_sponsor
- delete_sponsor
- update_contact
- create_speaker_task
- create_session
- assign_speaker
- manage_tracks
- manage_rooms
- set_submission_status
- decide_submission
- create_session_from_submission
- schedule_session
- check_in_attendee
- create_form
- update_form
- update_form_pipeline
- create_email_template
- invite_to_portal
- send_email
- request_media_upload
- create_event
- set_write_access
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.