WEVER LABS / CONNECTION GUIDES
Bring discovery and evidence checks into an agent workflow. Start with anonymous tools, evaluate the tenant connection, then consider paid capabilities with a wallet-aware client.
Documentation and endpoint evidence checked October 8, 2026. No Microsoft listing, certification or tenant installation is claimed.
Microsoft 365 Copilot is an AI assistant for work across Microsoft 365 experiences. Federated connectors let it retrieve external information through MCP without first indexing that information into Microsoft 365. For operators and tenant admins, Wever offers service discovery, checks of supplied evidence and a separate catalog of paid workflows.
Microsoft documents connector support in Copilot Chat, Excel, Cowork and Researcher. Availability depends on the experience, rollout and tenant policy. Its overview now describes write actions beginning rollout in early October 2026; Researcher remains read-only. The submission guide still requests read-only annotations and calls Word and PowerPoint forthcoming, while the overview lists them. These pages are not fully aligned. This guide promises no write or payment capability in a particular tenant. Current Microsoft overview ↗
01 / CHOOSE YOUR ENDPOINT
No authentication, account, wallet or Authorization header. This is the zero-friction start, separate from the paid catalog’s wallet allowance.
Its anonymous, read-only scope makes it our natural federated Gallery candidate. Candidate means proposed, not Microsoft approved. Tool titles, search/fetch expectations and package eligibility still require a submission review.
As of October 8, 2026. Standard access costs 0.10 USDC per call through x402 on Base mainnet after the shared 10 free calls per wallet per rolling 30 days. Existing subscription coverage and tool-specific authority requirements still apply.
Consider this catalog after evaluating the free connection. A signed wallet proof is required for the wallet allowance. Adding a URL does not authorize payments, principal transfers or escrow actions.
02 / TEST INSIDE YOUR TENANT
A Global Administrator or AI Administrator can use Microsoft’s custom federated connector flow. The documentation supports No Auth, which matches Wever’s free endpoint.
https://weverlabs.com/mcp-free.Have company, documentation, privacy and terms information ready. This is tenant configuration, not a public Gallery submission. Microsoft’s current setup and rollout instructions ↗
03 / UNDERSTAND DISTRIBUTION
Microsoft currently accepts rolling submissions. The current English submission page directs ISVs to Partner Center plugin packaging, followed by certification and Microsoft rollout. Tenant administrators then approve partner connectors. It no longer presents a separate public submission-form route. There is no documented 2 to 4 week guarantee.
Prepare a public HTTPS MCP endpoint; readable tool titles and readOnlyHint annotations; registered OAuth credentials for authenticated scenarios; reviewer access and setup instructions; at least three prompts with expected results; an 80-character description, up to 10 synonyms, 192 × 192 color and 32 × 32 outline logos; documentation, privacy and support links. A Partner Center developer or manager account is required.
Reserve the name, complete pricing/availability, properties, ratings and listing, upload the package, add certification notes and submit. Microsoft checks the artifacts and coordinates validation and rollout. Ongoing security maintenance and support are required. The page’s OAuth metadata table and authenticated-only prerequisite differ; confirm anonymous submission requirements with Microsoft. Official submission requirements ↗
A declarative-agent app is a different artifact: an app manifest and icons, a declarative agent manifest, and referenced plugin configuration. API-based plugins also reference an OpenAPI description. The app package goes to an administrator for organizational distribution or Partner Center for AppSource. Do not substitute a client connector JSON file for those manifests. Microsoft 365 app model ↗
Current public-publishing guidance requires enrollment in the Microsoft 365 and Copilot program, an eligible offer/package type, listing and legal information, and certification. Eligibility depends on the package and target experience. A working MCP endpoint does not establish eligibility. Public Marketplace publishing ↗
For MCP actions within a declarative agent, the plugin manifest is separate from an agent connector registered through agentConnectors in the app manifest. These are not interchangeable connector configurations. MCP plugins and agent connector distinction ↗
Organizational testing and upload depend on the authoring tool and package type. The admin center supports internal distribution; the federated submission page also describes signed device-package sideloading. That is not a generic MCP JSON upload. Follow the exact package’s supported procedure before certification. Organizational publishing guidance ↗
04 / COPY A CLIENT REFERENCE
These are complete VS Code .vscode/mcp.json configurations for its MCP client, useful for endpoint inspection with GitHub Copilot in VS Code. They are reference configurations, not Microsoft 365 upload manifests, Gallery submissions or declarative-agent packages. Using them does not install Wever into Microsoft 365 Copilot. Official client schema reference ↗
{
"servers": {
"wever_free": {
"type": "http",
"url": "https://weverlabs.com/mcp-free"
}
}
}{
"servers": {
"wever_paid": {
"type": "http",
"url": "https://weverlabs.com/mcp"
}
}
}Both endpoints use MCP POST requests. A browser GET can return 405 and is not a tool-discovery test.
05 / EXPLORE THE TOOLS
The free catalog contains wever_agent-daily-operator-brief, check_evidence_inventory, review_mcp_manifest, build_operator_brief, prepare_work_order and wever_tool_catalog. These prepare and inspect information; they do not execute a funded order.
The full catalog adds trust and permission checks, asset discovery, payment inspection, work orders, escrow, payouts and disputes. Read each contract. Evidence checks evaluate supplied material within stated bounds and do not certify an agent.
On October 8, 2026, the dashboard reported zero verified external usage across retained covered history. Company-authored operational work and synthetic tests are excluded from verified external totals and are never counted as adoption. Anonymous calls are outside that coverage, so zero does not mean no traffic.
Protocol availability is verified separately from Microsoft tenant compatibility. No Microsoft approval, paid Copilot execution, revenue or external adoption is claimed. Read current coverage and attribution limits ↗