Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Tip
Recommended: Start with Work IQ Dev Tools for supported pro-code declarative-agent and plugin scenarios. See the WIQD quickstart. Toolkit-based instructions remain available for existing projects and workflows that require them. Check capability and target-experience support before choosing a tool: WIQD doesn't target custom engine agents.
For Model Context Protocol (MCP) servers or APIs that don't require any authentication, or for developer environments where authentication isn't yet implemented, plugins can access the MCP server or API anonymously.
This article uses MCP plugins as the default walkthrough. The same steps apply to API plugins built from an OpenAPI document, except where noted.
Unlike the other authentication schemes, anonymous access requires no registration, credentials, or auth config - you set the authentication type to None directly in the plugin manifest.
Use Work IQ Dev Tools (recommended)
When adding an MCP action, use wiqd agent add action with the server's HTTPS endpoint in --mcp-server-url and select --mcp-auth-type none. This is also the command's default MCP authentication type. No auth config registration is needed. See the WIQD action command guidance.
For an existing plugin manifest, use the None configuration below. The wiqd agent add auth command doesn't offer an anonymous authentication type.
Add anonymous authentication to the plugin manifest
When you add an MCP server that requires no authentication in Microsoft 365 Agents Toolkit or through the declarative agent developer skill, the plugin manifest is set to None for you. Set it manually only when you edit an existing plugin manifest yourself.
To configure anonymous access, set the type property of the runtime authentication object to None.
"auth": {
"type": "None"
},
Note
Anonymous access is intended for development and testing. Add authentication before you deploy your plugin to production.