mcpField
A
AgendaForge

AgendaForge

VerifiedFeaturedRemote
agendaforge.appProductivity0Updated 9w ago
DocsRepositoryVisit website

About AgendaForge

AgendaForge provides remote MCP servers for reading and managing event data, including sessions, speakers, agendas, forms, and submissions. Reads run directly, while proposed changes and outbound messages require human approval in AgendaForge.

Key features

  1. 01Read event and agenda data
  2. 02Manage sessions, speakers, and rooms
  3. 03Access forms and submissions
  4. 04Propose changes for human approval
  5. 05Propose outbound communications for approval
  6. 06Search and fetch public documentation

Use cases

  1. 01Review event schedules and speakers
  2. 02Inspect CFP forms and submissions
  3. 03Prepare event changes for approval
  4. 04Look up AgendaForge documentation

MCP support

Provides hosted remote MCP servers over Streamable HTTP: an authenticated event-management server, a read-only variant, and a public documentation server. Write operations and outbound communications create proposals that require human approval.

#agendaforge#productivity#event-management#event-management-mcp#manage-event-from-claude

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.agendaforge.app/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

55

This tool takes no parameters.

Details

From the project README

AgendaForge MCP Servers

Official remote Model Context Protocol servers for AgendaForge, the AI-native event management platform.

Both servers are hosted, remote-only (Streamable HTTP), and published in the official MCP registry under the app.agendaforge namespace. There is nothing to install; paste the URL into any MCP-ready client.

Main server

https://mcp.agendaforge.app/mcp
  • Auth: OAuth 2.1 with dynamic client registration (WorkOS AuthKit). Scoped API keys are also supported for server-to-server use.
  • Registry name: app.agendaforge/agendaforge
  • What it does: read and manage your events, sessions, speakers, agendas, tracks, rooms, forms, submissions, contacts, and communications. Read tools execute directly. Every write and every outbound communication creates a proposal that a human approves inside AgendaForge before anything changes.
  • Read-only variant: https://mcp.agendaforge.app/mcp/readonly exposes only the read tools.
  • Anonymous initialize and tools/list are supported so agents can inspect the catalog before authenticating. tools/call always requires auth.

Public docs server

https://mcp.agendaforge.app/mcp/docs
  • Auth: none.
  • Registry name: app.agendaforge/docs
  • What it does: search_docs and fetch_doc over AgendaForge's public documentation and marketing content.

Discovery surfaces

Support

Questions or issues: open an issue here or see agendaforge.app/contact.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.