Grant AI access to your RevCent account via the RevCent MCP Server. The RevCent MCP server allows AI to retrieve information and perform specific actions using available MCP tools. Useful for MCP clients and AI Agents that wish to access protected resources. You can easily limit the AI's access to specific operations via permissions.
The MCP (model context protocol) allows AI to connect directly to RevCent and conduct operations. Operations include retrieving data, updating data, reporting and much more. AI has become smart enough to understand the entire RevCent ecosystem and the various caveats, therefore allowing users to grant AI access to their RevCent account via MCP is a big win for all.
- You create an OAuth client in RevCent specific to an AI use case.
- You add a custom MCP to your AI client/agent.
- You interact directly with your RevCent account using AI or build automations backed by AI, all connected to the RevCent MCP.
- Create multiple OAuth clients with limited permissions specific to use cases, i.e. personal client, reporting client, monitoring client.
The use cases are almost infinite, but below are a few basic ways in which to use AI connected to the RevCent MCP.
- Run on-demand reports using natural language, i.e. “what was my sales volume today versus yesterday”, or “whats my projected subscription revenue this month”.
- Have AI create your own reporting system, which runs queries directly using the RevCent MCP, then display or notify continual updates.
- Have your own AI agents continually monitor and take potential action on anything that occurs in your RevCent account, i.e. new sales, subscription renewals, etc.
- Create marketing specific AI agents, that analyze RevCent sales metadata to determine the best acquisition channels and cost effective marketing spend.
In a few steps you can connect AI to your RevCent account and give access to over 250 operations. You can limit access via permissions, which we recommend.
The RevCent MCP server url is https://mcp.revcent.com
In order for AI to access the RevCent MCP you must first create an OAuth Client in RevCent. We recommend that you create an OAuth client specific to each MCP client which will connect to the RevCent MCP server. For example, if you have multiple agents running and using the RevCent MCP server, each agent should have its own RevCent OAuth client if possible, with permissions enabled only based on the agents' purpose.
- Create an OAuth Client in RevCent. When logged into RevCent, go to https://revcent.com/user/oauth-clients and click the Create New OAuth Client button.
- You can create multiple OAuth clients which are limited in scope to specific AI use cases.
- Give the OAuth Client a name depending on the AI client/use case so you can track usage and reference it later.
- After creating the OAuth client you will be forwarded to the edit OAuth client page for the new client.
- On the edit OAuth client page, click the Auth Details tab.
- You will see both the Client ID and Client Secret.
- In your AI tool of choice, add an MCP server, with the URL being
https://mcp.revcent.com and enter the Client ID and Client Secret from step 5.
- Your AI tool should connect to the RevCent MCP server and initiate an authorization.
- Once you give the MCP server authorization it will have access to your RevCent account.
- If necessary, you also have the option to manually create an OAuth access token specific to a client if your AI tool only accepts an access token without OAuth configuration
- Please read the permissions section below.
Important: When AI accesses the MCP server, it can conduct over 250 operations in your RevCent account, some of which have serious consequences. This can be dangerous, so you should enable only the permissions the MCP server will need via OAuth Client permissions. Read more about setting OAuth Client level permissions
We recommend using the principle of least privilege (PoLP) when creating OAuth clients for MCP use. An OAuth client being used for MCP should only be allowed to do what it is intended, i.e. prevent unintended operations due to AI hallucinations.
Create an OAuth client for each specific AI use. You can create as many OAuth clients as you want.
- An OAuth client specifically for your personal AI interaction.
- An OAuth client specifically for a reporting agent.
- An OAuth client specifically for a monitoring agent.
Each OAuth client you create should only have the permissions enabled for operations it needs. Depending on its use case, only the operations it needs should have the respective permission enabled.
- A personal OAuth Client should only have permissions you intend to use for your AI interactions.
- A reporting agents' OAuth client should only have reporting based permissions. I.e. no refunds, edit, delete, etc. operations.
- A monitoring agents' OAuth client should only have reporting and detail retrieval based operations. I.e. no refunds, edit, delete, etc. operations.