ENDPOINT 1
https://api.vennio.app/mcp
MCP server metadata
- Name
- Vennio Scheduling
- Version
- 1.2.0
Known tools 24
propose_meetingCreate a multi-party meeting proposal with one or more proposed time slots.
Potential side effectsget_proposalRetrieve a proposal by ID, optionally including the full negotiation thread.
Inferred read-onlycheck_consentCheck whether you have consent to access another principal's data (e.g.
Inferred read-onlyget_networkGet a summary snapshot of your connection network: total connections, consent counts, recent contacts, and breakdown by relationship type.
Inferred read-onlylist_connectionsList your network connections with optional filtering by relationship type, status, or name/email search.
Potential side effectsget_meReturn the authenticated principal's identity: ID, name, email, and workspace ID.
Potential side effectsregister_webhookRegister a webhook endpoint to receive real-time event notifications.
Inferred read-onlycreate_event_typeCreate a reusable booking template (event type) that defines the meeting name, duration, and settings.
Potential side effectsrespond_to_consent_requestAccept or reject a pending consent request addressed to you.
Inferred read-onlylist_consent_requestsList consent requests involving you: incoming (others requesting access to your data, for you to accept/reject) and outgoing (your requests to others).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vennio-scheduling]
url = "https://api.vennio.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vennio-scheduling": {
"type": "http",
"url": "https://api.vennio.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vennio-scheduling
Remote MCP URL: https://api.vennio.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vennio-scheduling": {
"url": "https://api.vennio.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vennio-scheduling": {
"type": "http",
"url": "https://api.vennio.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vennio-scheduling",
"transport": "streamable-http",
"url": "https://api.vennio.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.