Start for free. Sign up without a card and connect your chat, or create a test key for the API. Going live with something real asks for a quick check of your company first.

Use Hypamoon in Microsoft Copilot

Add the Hypamoon MCP server to Copilot Studio, to Microsoft 365 Copilot as a ready-made agent, or to GitHub Copilot in VS Code. Which address, which sign-in, and what Hypamoon does differently for Microsoft clients.

Where it works

It does not work in the Copilot app for consumers (copilot.microsoft.com) or in the Copilot app on Windows: they only offer Microsoft's own connectors.

The address

https://api.hypamoon.com/api/v1/mcp

Use this address for every Microsoft client, not /api/v1/mcp/full. Copilot Studio does not send the resource parameter when it signs in, so its token always belongs to /api/v1/mcp; on /full it would get a 401 again and again.

You can add ?via=copilot-studio, ?via=m365 or ?via=vscode to tell us where the connection came from. That only counts for our numbers; it changes nothing about the tools or the sign-in.

Copilot Studio

1. Open your agent and turn on generative orchestration (Settings, Generative AI). Copilot Studio only uses MCP tools with it on.
2. Go to Tools, Add a tool, New tool, Model Context Protocol.
3. Fill in:
   • Server name: Hypamoon
   • Server description: Publishes sites, stores form entries, checks domains and deploys apps on Hypamoon. The agent reads this to decide when to use Hypamoon.
   • Server URL: https://api.hypamoon.com/api/v1/mcp?via=copilot-studio
4. Authentication: OAuth 2.0, then Dynamic discovery. Copilot Studio finds our sign-in from the address and registers itself; there is no client ID or secret to fill in.
5. Create the connection and sign in to Hypamoon. On the consent screen, pick your test project first and what the agent may do.
6. Under the tool, choose which Hypamoon tools the agent may use. With Allow all off, tools Hypamoon adds later stay off until you turn them on.

What to know:

• Copilot Studio uses MCP tools and resources, not prompts.
• The data policies (DLP) for Power Platform connectors also apply to an MCP server, so your admin may have to allow it.
• According to Microsoft, an agent's actions cost Copilot Credits, except for people with a Microsoft 365 Copilot license who use the agent as themselves.
• An API key works too: authentication API key, as a header named Authorization, and each user enters Bearer followed by their Hypamoon key (see Authentication). OAuth is the better choice: every user signs in with their own account and picks the project.

Microsoft 365 Copilot: the Hypamoon agent

A declarative agent brings Hypamoon into Copilot Chat and Teams for everyone in your organization that your admin assigns it to. According to Microsoft, an agent with actions also works in Copilot Chat for people without a Microsoft 365 Copilot license.

The package: ask for it at hypamoon.com/support and we send it to you. It is a Microsoft 365 Agents Toolkit project with the app manifest, the agent (name, instructions and four conversation starters), the action and the icons. There is no key or secret in it. Its README has every step and the fields to check in your version of Agents Toolkit.

In short:

1. Open the folder in VS Code with Microsoft 365 Agents Toolkit 6.12 or later.
2. Get an OAuth registration for the action. With Agents Toolkit: Add an Action, Start with an MCP Server, the address https://api.hypamoon.com/api/v1/mcp?via=m365, then OAuth (dynamic registration). Agents Toolkit registers itself at https://api.hypamoon.com/oauth/register. Or register a client yourself and add it in the Teams Developer Portal; the README shows how.
3. Provision. Agents Toolkit builds the app package and sideloads it for you. Your tenant needs custom app upload and Copilot access turned on.
4. Open Copilot Chat, pick Hypamoon under Agents, and sign in when it asks.

To give it to your organization, publish it from Agents Toolkit or upload the app package; an admin approves it in the Microsoft 365 admin center under Agents and assigns it to people or groups. An admin can also block it there.

A declarative agent cannot use an API key for an MCP action: Microsoft only allows OAuth or single sign-on there.

The action itself, if you build your own agent instead of using ours:

{
  "type": "RemoteMCPServer",
  "auth": { "type": "OAuthPluginVault", "reference_id": "<your OAuth registration id>" },
  "spec": { "url": "https://api.hypamoon.com/api/v1/mcp?via=m365" },
  "run_for_functions": ["*"]
}

VS Code and GitHub Copilot

In .vscode/mcp.json (this workspace), or with MCP: Add Server in the command palette:

{
  "servers": {
    "hypamoon": {
      "type": "http",
      "url": "https://api.hypamoon.com/api/v1/mcp?via=vscode"
    }
  }
}

Start the server and VS Code opens the Hypamoon sign-in in your browser. VS Code registers itself (dynamic client registration, since VS Code 1.101). Then use Copilot Chat in agent mode. Or use Add to VS Code on hypamoon.com/connect.

With an API key instead of OAuth:

{
  "inputs": [
    { "type": "promptString", "id": "hypamoon-key", "description": "Hypamoon API key", "password": true }
  ],
  "servers": {
    "hypamoon": {
      "type": "http",
      "url": "https://api.hypamoon.com/api/v1/mcp?via=vscode",
      "headers": { "Authorization": "Bearer ${input:hypamoon-key}" }
    }
  }
}

The GitHub Copilot coding agent (the one that works on issues in GitHub) cannot sign in to a remote server with OAuth. Give it a test key, or a live key with only the scopes it needs, as a repository secret whose name starts with COPILOT_MCP_, and send it in the Authorization header.

What Hypamoon does for Microsoft clients

Hypamoon recognizes Microsoft clients by their OAuth client (the address it returns to after sign-in, such as Copilot Studio's consent address, Teams or VS Code, and the name it registers with) and by the User-Agent it sends. Adding ?via= does not make a client recognized. For a recognized client:

• A smaller set of tools. Without ?tools=, you get a core of about 35 tools: the project, help, sites, forms and data, domain search, plus get_confirmation and get_task. See Choosing tools.
• Money waits for the owner. register_domain and transfer_domain only set up a confirmation: the tool answers with a link, https://app.hypamoon.com/confirm/<id>, the owner opens it and presses Confirm in the Hypamoon portal, and get_confirmation tells the agent whether it is done. refund_order answers with a link to the refund screen in the portal, and moving money on a marketplace is refused in the chat. Nothing is bought or refunded from Copilot directly. See Confirm in the portal.
• Long calls return a task. If deploy_site, deploy_app, move_to_live, an import or a similar call takes longer than about 25 seconds, the tool answers with status running and a task_id. The agent calls get_task with that task_id to read the result, which is kept for 24 hours.
• Schemas Copilot can read. The tool schemas have no type as a list and no exclusiveMinimum, two things Microsoft lists as known problems.

A client we do not recognize gets the standard behavior: every tool, and money tools that run directly with the scopes you gave. Signing in with OAuth from the clients above is the way to get the Microsoft behavior.

Choosing tools

Add ?tools= with one or more sets, separated by commas, to load more than the core:

https://api.hypamoon.com/api/v1/mcp?via=copilot-studio&tools=sites,domains,mail

Sets include sites, media, domains, data, phone, mail, mail_automation, commerce, discounts, stores, apps, agents, team and agency; list_toolsets lists them all with what they cover, and MCP explains each. ?tools=all gives every tool. Keep the list short: VS Code stops at 128 tools, and Copilot Studio may stop earlier (reports say 70). Your scopes still decide what the agent can do; a set only hides tools.

Not known yet

Until we have tested in a Microsoft tenant, these are open:

• How many tools Copilot Studio takes from one server (70 or 128).
• How long Copilot Studio waits for one tool call. That is why long calls return a task after about 25 seconds.
• Whether Copilot Studio and Microsoft 365 Copilot follow a change in the tool list (tools/list_changed). If you change ?tools=, add or provision the tool again so Copilot reads the new list.