How depfac/bevault-mcp-server works
beVault MCP exposes beVault’s Build, Source, and Distribute operations, with optional OIDC-protected States operations. An MCP client invokes registered tools; the tools use domain clients to call the corresponding beVault APIs and return tool responses. The graph groups documented capabilities even where individual tool implementations were not sampled; those edges are documented at the README level rather than inferred from filenames.
Main entry points: __init__.py MetaVault facade · main.py MCP server · source_systems.py Source client · tools Execution and store tools
Components 22
MCP runtime
- MCP server
bevault_mcp/main.py - Settings and auth
bevault_mcp/config.py
MetaVault
- Build tools
bevault_mcp/metavault/tools - Source tools
bevault_mcp/metavault/tools - Distribute tools
bevault_mcp/metavault/tools - Model search
bevault_mcp/metavault/tools/search.py - Mapping tools
bevault_mcp/metavault/tools/mappings.py - MetaVault facade
bevault_mcp/metavault/client/__init__.py - Model client
bevault_mcp/metavault/client/model.py - Source client
bevault_mcp/metavault/client/source_systems.py - Mapping client
bevault_mcp/metavault/client/mappings.py - Information mart client
bevault_mcp/metavault/client/information_marts.py - Project client
bevault_mcp/metavault/client/projects.py
States
- State machine tools
bevault_mcp/states/tools/state_machines.py - Execution and store tools
bevault_mcp/states/tools - States clients
bevault_mcp/states/client
API contracts and HTTP
- Request and response models
bevault_mcp/metavault/models - States models
bevault_mcp/states/models - HTTP transport
bevault_mcp/shared/http.py
Other components
- MCP client
- MetaVault API
- States API
Connections 29
- MCP client → MCP server: invokes tools
README.md - MCP server → Settings and auth: loads configuration
bevault_mcp/main.py - MCP server → MetaVault facade: initializes client
bevault_mcp/main.py - MCP server → States clients: initializes client
bevault_mcp/main.py - MCP server → Build tools: registers tools
bevault_mcp/main.py - MCP server → Execution and store tools: registers tools
bevault_mcp/main.py - Build tools → MetaVault API: performs operations
README.md - Source tools → MetaVault API: manages sources
README.md - Distribute tools → MetaVault API: manages marts
README.md - Model search → MetaVault facade: searches model
bevault_mcp/metavault/tools/search.py - Mapping tools → MetaVault facade: uses client
bevault_mcp/metavault/tools/mappings.py - MetaVault facade → Model client: provides resource
bevault_mcp/metavault/client/__init__.py - MetaVault facade → Source client: provides resource
bevault_mcp/metavault/client/__init__.py - MetaVault facade → Mapping client: provides resource
bevault_mcp/metavault/client/__init__.py - MetaVault facade → Information mart client: provides resource
bevault_mcp/metavault/client/__init__.py - MetaVault facade → Project client: provides resource
bevault_mcp/metavault/client/__init__.py - Model client → MetaVault API: calls API
README.md - Source client → MetaVault API: calls API
bevault_mcp/metavault/client/source_systems.py - Mapping client → MetaVault API: calls API
README.md - Information mart client → MetaVault API: calls API
README.md - State machine tools → States clients: uses client
bevault_mcp/states/tools/state_machines.py - Execution and store tools → States API: orchestrates states
README.md - States clients → States API: calls API
README.md - Model search → Request and response models: uses models
bevault_mcp/metavault/tools/search.py - Mapping tools → Request and response models: uses mapping models
bevault_mcp/metavault/tools/mappings.py - State machine tools → States models: uses models
bevault_mcp/states/tools/state_machines.py - Execution and store tools → States models: formats responses
bevault_mcp/states/tools/executions.py - Source client → HTTP transport: uses HTTP verbs
- MetaVault API → MCP client: returns results