You need one thing: the server URL.
https://mcp.eventa.live/mcp
Public tools work immediately. The first time you ask for something personal, the assistant sends you to Eventa to sign in and approve access.
Claude
- Open Settings → Connectors → Add custom connector.
- Enter the name Eventa and paste the server URL.
- Choose Connect. When you need something personal, you are sent to eventa.live to sign in and approve.
- Ask: "What's on in Dhaka this weekend?"
Claude Code
Add the server with one command, then check it:
claude mcp add --transport http eventa https://mcp.eventa.live/mcp
claude mcp list
Inside a session, /mcp shows the connection and lets you sign in to the personal tools.
Cursor
Add the server to your MCP configuration file:
{
"mcpServers": {
"eventa": {
"url": "https://mcp.eventa.live/mcp"
}
}
}
VS Code
Add it to the workspace file .vscode/mcp.json:
{
"servers": {
"eventa": {
"type": "http",
"url": "https://mcp.eventa.live/mcp"
}
}
}
MCP Inspector
The Inspector is the quickest way to look at every tool and try the sign-in flow.
npx @modelcontextprotocol/inspector
Choose the Streamable HTTP transport, enter the server URL and connect. Select Tools → List tools to see what is available without signing in, then run list_events with limit set to 3.
Without any client: raw requests
The server speaks plain JSON-RPC over HTTP, so you can check it with curl. Send both Accept types.
curl -s https://mcp.eventa.live/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
The reply names the server and lists its capabilities:
{"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"prompts":{"listChanged":true}},"serverInfo":{"name":"eventa","title":"Eventa","version":"0.2.0"}},"jsonrpc":"2.0","id":1}
Call a tool the same way:
curl -s https://mcp.eventa.live/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search","arguments":{"query":"concert","limit":1}}}'
Results arrive both as readable text and as structuredContent that matches the tool's declared output schema, so your code can use either.
Two things to know
- The server is stateless: there are no sessions to open or close, and
GETandDELETEon the endpoint answer405. - A request for a personal tool without a token answers
401with aWWW-Authenticateheader that tells a standard client where to sign in. Read Authentication if you are building your own client.
Next steps
- Browse the tool reference for every argument and an example.
- Try the recipes for ready-made requests.
- If something does not work, see Limits and errors and the FAQ.