MCP stands for Model Context Protocol. It is a standard way for an AI agent to connect to external tools and data sources through defined capabilities, rather than relying on a separate custom integration for every connection.
Our current release of Command MCP (in beta) offers a secure, structured way to work with Value analyses and generate reports, via AI agents. Customers can connect their organisation’s approved AI workflows to use the business case data, calculations, templates, permissions, and methodology already configured in Mediafly Value Toolbuilder.
Note - Availability relies on your organisation’s acceptance of our AI terms. Command MCP respects your existing Mediafly user groups & permissions. As with any AI feature, always review important answers before using them externally.
On this page
- What is Command MCP?
- What can Command MCP do?
- Getting involved in the Command MCP beta
- Important beta considerations
- Command MCP - FAQs
What is Command MCP?
Command MCP is Mediafly’s MCP server for connecting compatible AI agents to Mediafly products and tools.
Command MCP is not a standalone chatbot or copilot. It is the connectivity layer that allows an approved AI agent—such as Claude, Gemini, Cursor, or another MCP-compatible client—to call Mediafly tools. The agent provides the conversation and reasoning, while Mediafly provides the underlying Value data, calculations, templates, permissions, and governed workflows.
What can Command MCP do?
In the initial beta, Command MCP for Value Toolbuilder supports workflows such as:
- Retrieving existing business case analyses
- Creating and updating Value analyses
- Working with the business case inputs and benefits available to the user
- Using existing Value frameworks, calculations, and report templates
- Generating reports from the connected agent
The exact actions and templates available to each user depend on their existing Mediafly access and the configuration of your Value Toolbuilder environment.
Getting involved in the Command MCP beta
If you are a Value Toolbuilder customer, please contact the Mediafly team via the Community, to discuss being involved in our Command MCP beta. This will include confirming that your organization is using an MCP-compatible AI client (eg. Claude).
If suitable, the Mediafly team will complete configuration and will confirm when your organisation is ready to begin testing. At this point, you will be provided with detailed guidance on how to turn Command MCP on, what to expect, and how to shape what we build next.
A small, controlled rollout for the beta is recommended. We suggest starting with administrators and a few user champions and gathering their feedback initially.
Important beta considerations
Command MCP is an early beta capability. The connected AI agent may interpret open-ended requests differently between conversations, and the same prompt may not always produce identical results. Workflows that depend on the agent to interpret additional context—such as call transcripts, CRM information, or web research—may also vary depending on the client and other connectors enabled by the user.
Mediafly-managed Value frameworks and calculations remain governed by the configured Toolbuilder methodology. As with any AI-enabled workflow, users should review important outputs before relying on them in customer-facing or business-critical materials.
Command MCP - FAQs
How do access and permissions work?
Command MCP uses the authenticated user’s Mediafly credentials. Users can access only the Value templates and analyses that they are already authorised to use.
Administrators should therefore treat Command MCP as an extension of the existing Toolbuilder permission model, not as a separate way to bypass access controls. Before enabling the beta, Admins should confirm that the intended test users have:
- Access to the relevant Toolbuilder environment or sandbox
- Permission to use the Value templates to create or update analyses included in the test
- Access or approval to the organisation-approved AI client used, for MCP connector setup (e.g. for enterprise managed plans on Claude, the plan admin has to set up an initial connector before each individual user can sign in to use it)
Replies have been locked on this page!