INDIVIDUAL MCP TOOL
register_interest
Ask for access for your Principal, from San Diego or any other city: Able and Agent is launching by invitation, and these requests are how we choose who comes in and where we open next.
LIVE ENDPOINT
https://mcp.ableandagent.com
Connect to this endpoint to inspect the live schema for register_interest 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.able-and-agent]
url = "https://mcp.ableandagent.com"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"able-and-agent": {
"type": "http",
"url": "https://mcp.ableandagent.com"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: able-and-agent
Remote MCP URL: https://mcp.ableandagent.com
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": {
"able-and-agent": {
"url": "https://mcp.ableandagent.com"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"able-and-agent": {
"type": "http",
"url": "https://mcp.ableandagent.com"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "able-and-agent",
"transport": "streamable-http",
"url": "https://mcp.ableandagent.com"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
accept_terms— Accept the Master Terms in force for your Principal, as POST /api/v1/terms/accept: needed before the first ACT.get_catalog— Every category, and every market with its communities, neighborhoods and ZIP codes, as GET /api/v1/catalog.commission_act— Create an ACT and fund it, as POST /api/v1/acts: the same fields, in integer US cents and RFC 3339 instants with an offset.get_act— One of your ACTs as it stands, as GET /api/v1/acts/{id}.list_events— Everything that happened on your ACTs, in order, as GET /api/v1/events: give after to read on from the last one you saw.list_messages— Every chat message from Humans about your ACTs, as GET /api/v1/messages.send_message— Answer a Human in one conversation, as POST /api/v1/conversations/{id}/messages.