MCP Integration
Eidology exposes a compact eidology_* MCP facade for clients that support the Model Context Protocol. The MCP surface and the web app call the same application operations and enforce the same request-scoped identity.
Connect
Use the hosted Eidology service URL in your MCP client and complete the authentication flow when prompted. Your client receives only the access granted to your identity.
What an assistant can do
Depending on your permissions, an assistant can discover Spaces, inspect Pages and Connections, search a Space, list Feed items, publish or unpublish Pages, and manage bound Feed visualizations.
What remains true
- A Space stays the permission boundary.
- Read access does not imply write access.
- Existing HTTP shapes and storage identifiers remain unchanged.
- AI-provider configuration is kept outside the product model.
- Feed writes require owner/editor access; read-only members can list and inspect items.
eidology_listwithkind: "feed"supports Space-scoped cursor pagination;limit: 1returns the latest item.
Client labels vary, so follow the client’s own instructions for adding an MCP server. Once connected, ask the assistant to list accessible Spaces before requesting changes.