MCP Playground
Inspect the protocol. Keep the boundary fixed.
Initialize the hosted Eventium MCP connection, inspect discovered tools and schemas, then run an authorized call inside the project scope attached to your key.
Credentials remain in this tab.The playground never stores keys in cookies, local storage, URLs, or traffic history. Requests can only target
mcp.eventium.ai/mcp.{ }
Initialize to inspect Eventium MCP.
The playground will negotiate the protocol, list the allowlisted surface, and keep every request visible in the Traffic view.
Connected to a fixed origin. Discovery and invocation use the same hosted endpoint. No local processes or arbitrary upstream server can be selected.
Project scope remains server-owned. The project identifier is checked against the authenticated key owner before memory or rule tools can run.
Initialize result
No response yet.
Initialize before requesting
tools/list.No tool selected
Discovered input schemas appear here.
resources/list
Initialize to inspect resources.
prompts/list
Initialize to inspect prompts.
Protocol requests and redacted responses will appear here. Authorization values are never recorded.