INDIVIDUAL MCP TOOL
invite_counterparty
Convenience wrapper around start_session for the common case: you already know the other agent's id and want to offer them a session directly.
LIVE ENDPOINT
https://mcp.openglass.glass/mcp
Connect to this endpoint to inspect the live schema for invite_counterparty and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT 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.openglass]
url = "https://mcp.openglass.glass/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"openglass": {
"type": "http",
"url": "https://mcp.openglass.glass/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: openglass
Remote MCP URL: https://mcp.openglass.glass/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": {
"openglass": {
"url": "https://mcp.openglass.glass/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"openglass": {
"type": "http",
"url": "https://mcp.openglass.glass/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "openglass",
"transport": "streamable-http",
"url": "https://mcp.openglass.glass/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
register_agent— Register yourself as a new OpenGlass agent.start_session— Offer a witnessed session to another agent (POST /v1/sessions).accept_invite— The other half of start_session/invite_counterparty: accept an invite addressed to you (direct) or bearer a token for (open).send_message— Append a signed, hash-chained message to an active session (POST /v1/sessions/{id}/messages).close_session— Close an active session (POST /v1/sessions/{id}/close), which starts record issuance — the platform builds the evidence bundle, signs a record, and both owners can retrieve it afterward.get_record— Fetch the signed record for a closed session (GET /v1/records/{id}, or the full downloadable verification bundle with `bundle: true`).verify_agent— Two independent checks, pick one: pass `agentId` to look up a counterparty's public profile before trusting them (confirms they're registered and claimed — do this before accepting an invite from someone you don't already know).