For members and developers
Connect your assistant
Your AI assistant can look up your community information for you. Read-only: it can see your account statement, the open votes and your records; it can never change anything.
For members
Connect your AI assistant to your community information. Read-only: it can see your account statement, the open votes and your records; it can never change anything. You decide what it can see, and you can disconnect it whenever you want.
01
Create a connection
On your Connections page you choose what your assistant can see and create a key. The key is shown only once: copy it.
02
Add it to your assistant
Paste the key into your AI assistant, wherever connections are set up. That links it to your information.
03
Ask it about your community
Now you can ask for your balance, see which votes are open, or check your records, in your own words.
For developers
El Pozo exposes a read-only MCP server. It is the same contract your assistant uses: any MCP-compatible client can connect with the member's key.
Endpoint
Authentication
Every request carries the Authorization header with the key the member created on their Connections page. The key starts with elpozo_ and is read-only, scoped and revocable.
Protocol
Model Context Protocol over JSON-RPC 2.0 via HTTP POST (the synchronous Streamable HTTP transport). The methods are initialize, tools/list and tools/call.
The six read-only tools
Write access: propose then confirm
With write scopes, an AI can PROPOSE actions (a payment, a due, an announcement) but never execute them: every proposal lands in the "To confirm" queue, and only a person with the matching role confirms it. A ":propose" scope creates proposals; a ":commit" scope confirms them only when the token holder already holds that role (scope AND role, never scope alone). Every token has caps (amount per proposal, proposals per day) and is revoked instantly. Writes are off until each community turns them on.
An AI can also bring a document in over the connection (with propose_from_document): a member list, a bank statement, some receipts. The document is treated as DATA, never as instructions — any text inside it that looks like a command is ignored — and becomes the same To-confirm proposals. Nothing is written until a person confirms each one.
Example MCP client config
Point your client at the endpoint and pass the key in the Authorization header.
{
"mcpServers": {
"elpozo": {
"url": "https://elpozo.mx/api/mcp",
"headers": {
"Authorization": "Bearer elpozo_your_key_here"
}
}
}
}curl example: the initialize call
A minimal call that opens the session and confirms the key works.
curl -X POST https://elpozo.mx/api/mcp \
-H "Authorization: Bearer elpozo_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-06-18",
"capabilities": {},
"clientInfo": { "name": "my-assistant", "version": "1.0.0" }
}
}'Everything is read-only and scoped to exactly what the member granted. There is no way to write or change data, and any connection can be revoked at any time from the Connections page.