MCP Configuration
MCP Overview
Understanding the Model Context Protocol integration in Praximos
MCP Overview
Praximos integrates with AI assistants through the Model Context Protocol (MCP) — an open standard that lets LLMs like Claude interact with your Praximos instance as a set of structured tools.
What is MCP?
MCP is a protocol that exposes application functionality as tools that AI models can discover, understand, and invoke. When connected to Praximos via MCP, an AI assistant can:
- Create and manage projects — set up new projects, update details, list existing ones
- Track obligations — create obligations, assign executors, monitor status
- Manage accounts — invite users, grant permissions, configure access
- Query data — retrieve projects, obligations, executors, and resolutions
All MCP operations run through Praximos's policy engine — the AI has exactly the same permissions as the authenticated user.
Architecture
Praximos exposes MCP tools through the ash_ai library, which maps Ash resource actions directly to MCP tool definitions. This means:
- Every exposed action becomes an MCP tool with auto-generated parameter schemas
- Descriptions from resource attributes become tool parameter descriptions for the AI
- Ash policies enforce authorization — no policy bypass is possible through MCP
- Validations run normally — the AI must provide valid inputs just like any other client
Available Tools
Praximos exposes tools across three domains:
Accounts
| Tool | Description |
|---|---|
accounts_create_account | Create a new account with owner |
accounts_get_account | Retrieve an account by name |
accounts_invite_user | Invite a new user to an account |
accounts_grant_permission | Assign READ/WRITE/MANAGE on projects |
accounts_revoke_permission | Remove a user's permission |
Projects
| Tool | Description |
|---|---|
projects_create_project | Create a new project |
projects_list_projects | List accessible projects |
projects_get_project | Retrieve a single project |
projects_update_project | Update project details |
projects_delete_project | Delete a project |
Obligations
| Tool | Description |
|---|---|
obligations_create_obligation | Create a new obligation |
obligations_list_obligations | List accessible obligations |
obligations_assign_executor_to_obligation | Assign an executor |
obligations_create_executor | Create a person/entity |
obligations_create_resolution_definition | Define resolution requirements |
Tip: Attribute descriptions in the Praximos codebase directly become parameter descriptions in MCP tools. This is why every attribute must have a description.