Monite MCP Server
This project provides a Monite MCP (Model Context Protocol) server that seamlessly integrates Monite's advanced AI functionalities as tools for AI agents and AI-driven applications. It offers a streamlined solution for Monite's onboarded clients to leverage AI-driven insights and automation with their financial data, enhancing operational efficiency and decision-making capabilities.
This server is specifically designed to be valuable and easily usable for Monite customers, allowing them to extend their Monite platform experience with powerful AI capabilities.
Status: The MCP server is ready for use but is under active development. New tools and features may be added, and existing ones might be refined.
Main Goals
- Provides a set of tools corresponding to various Monite AI features, exposed via as a MCP server.
- Enables easy integration with AI agent frameworks that support the MCP specification.
Prerequisites
The primary requirement for running the Monite MCP server is a Monite Authentication Service. This service is responsible for providing Entity User authentication tokens, which the MCP server uses to make authorized calls to the Monite AI API.
A Python example implementation of such an authentication service (auth_service.py) is available in the code_examples/ directory.
For comprehensive details on Monite's authorization levels and credential management, please refer to the Monite API Documentation.
Getting Started
This guide assumes you are familiar with the Monite API, possess partner credentials (CLIENT_ID and CLIENT_SECRET), and have an onboarded entity with existing data.
The Monite MCP server is intended for use with Monite Entity User tokens. Consequently, monite-mcp relies on an external authorization service that securely manages your CLIENT_ID and CLIENT_SECRET.
Environment Variables
A Monite MCP server instance requires the following environment variables to be configured:
AUTH_SERVICE_URL: The URL of your authentication service. This service must expose aGET /tokenendpoint that accepts anentity_user_idquery parameter and returns a Monite Entity User token.ENTITY_USER_ID: The ID of the Entity User for whom the MCP server will operate.MONITE_AI_API_BASE: (Optional) The base URL for the Monite AI API. Defaults to the Monite Sandbox environment:https://api.sandbox.monite.com/v1/mcp.
The AUTH_SERVICE_URL and ENTITY_USER_ID variables are mandatory for each Monite MCP server instance. Your CLIENT_ID and CLIENT_SECRET will be required by the authentication service itself (see example below).
Running the Example Authentication Service
The code_examples/ directory includes an example authentication service (auth_service.py). To run it:
- Ensure your
CLIENT_IDandCLIENT_SECRETare set as environment variables. - Navigate to the
code_examples/directory. - Execute the following command:
make run-auth-serviceThis will startauth_service.py, which the MCP server can then use to fetch tokens. By default, it runs onhttp://localhost:8888, so yourAUTH_SERVICE_URLwould behttp://localhost:8888/token.
Running the Monite MCP Server and Example Agents
The Monite MCP server communicates via standard input/output (stdio) and is typically started as a subprocess by an AI agent.
The code_examples/ directory contains pydantic_ai_agent.py and mcp_use_agent.py, which demonstrate how to instantiate and use the monite-mcp server with different agent frameworks.
These examples require
OPENAI_API_KEYin the environment :)
To run these examples (ensure the example authentication service is running first):
- Navigate to the
code_examples/directory. - Use one of the following commands:
- For the Pydantic AI example:
make run-pydantic-ai-agent - For the MCP-Use example:
make run-mcp-use-agent
- For the Pydantic AI example:
These commands will execute the respective agent scripts, which in turn start and interact with the monite-mcp server.
Active Development
This project is actively being developed. Contributions, bug reports, and feature requests are welcome!
Metadata
Release files for monite-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| monite_mcp-0.1.1.tar.gz | 102.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| monite_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.6 kB
Release files / monite_mcp-0.1.1.tar.gz
| Download URL | monite_mcp-0.1.1.tar.gz |
|---|---|
| Size | 102.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1316b25b4b9c7959af2f680816647c35040cee0860cdf2d2f1a3159ed86b92d
|
|
BLAKE2b-256 checksum How to use checksums |
a31f7f506c88551590457b2e2262313eeea2a3625c47d00d9300ef20611a7503
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.6
|
Release files / monite_mcp-0.1.1-py3-none-any.whl
| Download URL | monite_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7758bb53e23b11ec6e079624a15327cf1900ae8713fc7ea02d59fd15551d1b09
|
|
BLAKE2b-256 checksum How to use checksums |
768136e4031678e44909b3affa88edc0d3cad4ea3e42a93da3d94fa30d1eb68a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.6
|
Security for monite-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.