MCP Servers
Connect the public GridWonk plugin or maintain an approved organization integration.
description: Discover and use GridWonk MCP-compatible tools with stateful work-item continuity. last-updated: "2026-10-27"
The public GridWonk plugin connects an AI client to your selected workspace. Start with the customer MCP guide and Connected apps. The package needs neither an internal GridWonk account nor a private repository.
Choose the right connection
| Connection | Identity and scope |
|---|---|
| Public GridWonk plugin | Your verified user session, explicitly bound to one workspace in the browser |
| Existing organization integration | Organization credentials provisioned for the agreed API/MCP profile |
The catalogs differ. An integration key does not become a public-plugin user connection, and a public-plugin connection cannot access operator tools. Never copy credentials between them.
Hosted runtime
The endpoint is https://gridwonk.com/api/v1/mcp. Clients negotiate the supported protocol during
initialization. Existing organization integrations use their returned transport session. The public
plugin is stateless and reauthorizes its exact OAuth session on every call; it does not require a
new MCP transport session after browser confirmation. Use the exact protected-resource metadata
for interactive OAuth; do not substitute a machine-token issuer into a user sign-in flow.
When interactive sign-in is enabled, resource discovery advertises only its identity scopes.
Machine integrations discover partner.read and partner.write from their authorization
server's /.well-known/oauth-authorization-server document.
For the public plugin, complete the exact-session workspace confirmation when connection_status
asks for it. Its customer tool list stays stable across activation. Ordinary calls need current
membership, approval, role, and any required processing allowance. Revoke the existing connection
and finish provider cleanup before signing in again to select another workspace.
For an existing organization integration, follow API authentication
and use its assigned credentials. An organization's API access and usage limits still apply.
Only request operations shown by its credential-specific tools/list response. Caller-supplied
organization, actor, project, or document identifiers do not grant authority.
Working with packets
Use supported intake tools and returned upload instructions. Follow job and review status with
bounded polling, honoring Retry-After. Keep the same returned operation identity while recovering
from a transport interruption; a lost response does not prove that work failed or that no cost was
incurred. Unsupported or uncertain processing stops new work until it can be resolved.
The server decides which source formats your workspace can process. If your workspace is limited to PDF review, use standalone PDFs: images, ZIP archives, and native CAD files are refused, including when attaching an existing File Library item or starting a review of an existing packet. A client cannot override that refusal. A PDF-only review does not waive the utility's required evidence.
Keep the returned project, packet, upload, job, and review-run identifiers with the status or report they identify. When summarizing findings, preserve the report's source document and page citations. Use the existing identifiers to check interrupted work before starting another attempt; an upload receipt or completed document check is not a completed packet review.
The public plugin supports research, authorized draft preparation, eligible intake/review starts, and status/results. Formal submission, document-role decisions, adjudication, notice sending, membership administration, and purchases remain website workflows. Read-only access does not start processing. Review completion does not mean utility approval.
Discovery and troubleshooting
Public help and the public plugin contract describe customer capabilities. Complete docs-host OpenAPI/MCP documents and the operator catalog require native internal authorization. Approved organization integrations can retrieve their separately authenticated API contract as described in the API overview.
For connection problems, use Connected apps. For payment or allowance status, use trial and prepaid processing. Never post access tokens, credentials, or signed upload URLs in a conversation or support transcript.
Workspace appearance
Organization admins preview and save source-palette color schemes in the signed-in website. Appearance discovery and saving have no public or Admin MCP mutation tool. Finding logo colors does not approve a logo for display. See organization settings.