MCP Server: Microsoft Copilot Studio Connection Instructions

What You'll Need

• Access to Copilot Studio
• Maker rights in a Power Platform environment
• Your GovSpend API key
• Transport: Streamable HTTP (SSE is no longer supported)
• No DLP policy blocking custom connectors or MCP
• MCP endpoint: https://mcp-spark-prod.govspend.com/mcp

Critical: The single most common setup mistake is forgetting the Bearer prefix on the API key. Copilot Studio passes whatever you type directly into the Authorization header — without the word Bearer followed by a space in front of your key, GovSpend will reject every request with a 401 error. See Step 5 below.

Power Platform DLP note: Because MCP servers are accessed through Power Platform connector infrastructure, any DLP policy restricting custom or premium connectors will also restrict the GovSpend MCP. Coordinate with your Power Platform admin before setup if DLP policies are in play in your environment.

Step 1: Create a blank agent

Sign in to copilotstudio.microsoft.com. On the Agents list, click + Create blank agent (top right). You'll land in a new untitled agent.

Step 2: Open the Tools page

In the agent's left navigation, click Tools.

Step 3: Add a new MCP tool

Click Add a tool → New tool → Model Context Protocol. The "Add a Model Context Protocol server" dialog will appear.

Step 4: Fill in the form

The Server description is what the orchestrator reads to decide when to call the server. Keep it concrete — the text above is what we recommend.

Step 5: Create the connection — with the Bearer-prefixed key

On the connection row at the bottom of the dialog, click the Not connected dropdown → Create new connection. A password-style input will appear. Paste your value in this exact format:

Bearer YOUR_API_KEY 

Replace YOUR_API_KEY with the key from your GovSpend account (GovSpend → API Keys). The full value should look like:

Bearer ugheuoghebtuo2p48290ud2pidu2 

That is: the literal word Bearer, one space, then your key. Click Create.

If you omit the Bearer prefix, every request will fail with 401 Unauthorized and your tools will appear to do nothing. Copilot Studio uses the value exactly as typed as the full Authorization header.

Step 6: Add and configure

Back on the tool screen, click Add and configure. The Spark MCP page opens with Details and Tools sections. Expand Tools — you should see every GovSpend tool listed (analytics_bids, search_contracts, search_federal_contracts, etc.). The connector toggle at the top should read Enabled.

Step 7: Pick the model

Click the back arrow to return to the agent, then open the Overview tab. Under Select your agent's model, choose your preferred model and save.

Step 8: Write the system prompt

On the Overview tab, click Edit next to Instructions and paste your system prompt. Save.

Step 9: Test and publish

In the Test your agent pane on the right, try a question like:

What are the top 10 vendors selling cybersecurity services to Texas state agencies in the last 12 months?

When you're satisfied with the results, click Publish and share the agent with the users or groups who should have access.

Troubleshooting

Every request returns 401 Unauthorized

• Most common cause: missing Bearer prefix. Delete the connection (make.powerapps.com → Connections), then re-create it with the value Bearer YOUR_API_KEY.
• Confirm the URL is pasted exactly — no trailing slash, no http://, no extra path beyond /mcp.
• Verify your GovSpend API key is valid and your subscription includes MCP access. Generate a fresh key from GovSpend → API Keys if needed.
• Check that the Header name is exactly Authorization (capital A, no typos) and that Type is set to Header, not Query.

I don't see "Model Context Protocol" as a tool type

• The agent doesn't have generative orchestration enabled. Go to Settings → Generative AI, switch to Generative, then refresh.
• Your tenant or environment may be on an older Copilot Studio release that predates MCP support. Contact your Power Platform admin about updating.

Connection saves fine but the agent never calls GovSpend

• Open the Spark MCP tool page and confirm the Tools section lists tools. An empty list means the connection didn't authenticate — re-check the Bearer prefix.
• Confirm the agent's orchestration is set to Generative under Settings → Generative AI. Topic-only and classic agents won't call MCP tools.
• If the Server description is too vague, the planner won't route to GovSpend. Use the recommended description from Step 4.
• Try a more specific question. Very broad questions sometimes don't trigger any tool.

"Connector blocked by DLP policy"
Your Power Platform environment has a DLP policy preventing custom or premium connectors. Your Power Platform admin needs to allow the GovSpend MCP connector for the environment your agent lives in.

Does each user need their own connection?
By default, yes — each user creates their own connection using their own GovSpend API key, and every API call is attributable to that GovSpend user, respecting their entitlements. For a shared service-account connection, contact support@govspend.com.

Need to change the URL or rotate the key

• For URL changes: remove the MCP tool from the agent (Tools → three-dot menu → Remove) and re-run setup.
• For key rotation: go to make.powerapps.com → Connections, delete the existing connection, and re-create it with the new Bearer KEY value.