MCP server discovery questionnaire

Mission Control | Managed Intelligence Provider

An AI assistant is only as useful as the systems and data it can reach. An MCP (Model Context Protocol) server is that connection: it lets your AI assistant look things up and take actions in your systems through a controlled set of "tools", with a full record of each request, response and tool call. Answer what you can; "not sure" is a useful answer.

Do not enter passwords, API keys, tokens or other secrets in this form. We'll arrange a secure channel for anything sensitive.

Your details

1. Organization and project overview

This section sets the business context: why the project exists and who decides.

1.2Which locations or regions will use this service?

2. AI provider and how people use it

The AI provider and the apps your people use determine how the MCP server connects and signs users in.

2.1Which AI provider(s) do you use today?
2.2Which plan or license tier are you on?
2.3Does your AI plan support connecting custom MCP servers today?
2.4Does your AI provider account have data-retention or "no training on our data" settings already agreed?

3. Scope, tasks and pain points

This is the most important section: these answers determine the complexity and scalability of the project.

3.1Should the AI only read and summarize information at first, or also create, update or delete records?

4. Systems inventory

List every system the AI might need to read from or act in, and who controls it. "Vendor" means a SaaS product the vendor runs (Salesforce, Microsoft 365); "internal" means something your team built or hosts. Consider email and calendar, file storage, CRM, ERP and accounting, ticketing and helpdesk, HR and payroll, project management, e-commerce, telephony, data warehouse, and custom line-of-business apps.

System 1

5. Sign-in, permissions and security

The AI should never see more than the person using it is allowed to see. These answers decide how we enforce that.

5.1Which identity provider do your people sign in with?
5.2Is single sign-on and multi-factor authentication required for this service?
5.3Should each user's own permissions in each system apply, or will one shared service account be used?
5.6Do you require a security review, penetration test or vendor risk questionnaire before go-live?
5.10Should destructive actions (delete, bulk update, sending to external recipients) be blocked entirely, or allowed only with confirmation?
5.11Should we enforce rate or volume limits per user or per tool to limit damage from a compromised account or runaway automation?

6. Compliance, privacy and data location

Regulations you follow shape what data the AI may see, where logs live, and how long they are kept.

6.1Which regulations or frameworks apply?
6.2What types of sensitive data sit in the systems listed?
6.6Will contracts need a data processing agreement or business associate agreement?
6.8Do you need the ability to delete a specific person's data from logs on request?

7. Hosting and infrastructure

Where the server runs affects cost, security review and who maintains it.

7.1Where should the MCP server run?
7.5Do you need separate development, test and production copies of the server?

8. Support and ongoing operations

After launch, systems change and new needs appear. These answers define who keeps the service running and how.

Helpful to share

Don't upload these here. Tick what you have and we'll set up a secure channel.

Documents available