mcp-create-declarative-agent

Generates declarative agent projects for Microsoft 365 Copilot integrating MCP servers.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill mcp-create-declarative-agent-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-create-declarative-agent
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/mcp-create-declarative-agent
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill mcp-create-declarative-agent-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Microsoft 365 Copilot declarative agent that connects to a Model Context Protocol (MCP) server requires manually authoring multiple interdependent manifest files, configuring OAuth authentication, and mapping tool definitions, which is error-prone and time-consuming. ## Core Features & Use Cases - Project Scaffolding: Generates the complete appPackage structure including manifest.json, declarativeAgent.json, and ai-plugin.json wired for MCP runtimes. - Authentication Configuration: Sets up OAuth 2.0 (OAuthPluginVault) or SSO authentication with environment variable templates for credentials. - Tool Import & Response Mapping: Imports selected MCP server tools and defines response_semantics for extracting structured data from API responses. - Use Case: A developer wants to expose their company's Jira MCP server to Microsoft 365 Copilot so users can query and create issues via natural language; this Skill generates the full agent package, auth config, and testing instructions. ## Quick Start Ask the agent to create a declarative agent for Microsoft 365 Copilot that connects to your MCP server URL with OAuth authentication and selected tools.

Frequently Asked Questions about mcp-create-declarative-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a declarative agent for Microsoft 365 Copilot with an MCP server?

Scaffold a declarative agent using Microsoft 365 Agents Toolkit, add an MCP action pointing to your server URL, select the tools to import, and configure authentication. The toolkit generates manifest.json, declarativeAgent.json, and ai-plugin.json with MCP runtime definitions.

What authentication methods does an MCP declarative agent support?

MCP-based declarative agents support OAuth 2.0 via OAuthPluginVault with a reference ID, client credentials, and scopes, or Single Sign-On (SSO). Credentials are stored in environment files like .env.local rather than hardcoded in manifests.

What files are generated for a Copilot declarative agent project?

The project includes appPackage/manifest.json for the Teams app definition, declarativeAgent.json for agent instructions and capabilities, ai-plugin.json for MCP function and runtime definitions, and .vscode/mcp.json linking the server URL to the plugin file.

Why are my MCP tools not appearing in the Copilot agent?

Tools may be missing if mcp.json points to the wrong server URL, tools were not selected during import, or ai-plugin.json lacks correct function definitions. Re-fetch actions from the MCP server if its tool set changed.

How do I test a declarative agent before deployment?

Provision the agent in Agents Toolkit, start debugging to sideload it in Teams, then test in Microsoft 365 Copilot at m365.cloud.microsoft/chat. Authenticate when prompted and validate each exposed function with natural language queries.