workiva-mcp
An MCP server for the Workiva platform that pairs API tools with a knowledge base of confirmed API behavior, automatically attaching fixes to failing API calls, and supporting SQL execution and other Wdata operations.
README
workiva-mcp
An MCP server for the Workiva platform that pairs API tools with an accumulating knowledge base of confirmed API behaviour — the quirks, dead ends, and undocumented requirements that otherwise cost every agent (and every teammate) the same hour of rediscovery.
The mechanism that makes the pairing matter: failing API calls
automatically attach the matching KB entry. An agent that hits
400 "unable to match urn" gets the fix inside the error message itself,
without ever knowing the KB exists.
Status: v0.1.0 — the full planned surface is live: 20 tools across the KB, Wdata, Graph and Spreadsheets, plus the escape hatch and the drafts → PR contribution loop.
Install
claude mcp add workiva -- uvx --from git+https://github.com/woof-xyz/workiva-mcp@v0.1.0 workiva-mcp
Add -e WORKIVA_ALLOW_WRITES=1 before -- to enable write tools (see
Write safety). Pin a tag — uv caches git resolutions, so an unpinned
main silently freezes at whatever commit it first resolved. Upgrading =
re-add with the new tag. Credentials go in ~/.workiva/credentials
(Credentials below); the KB tools work with no credentials at all.
Tools
| Group | Tools |
|---|---|
| KB | kb_search · kb_list · kb_get · kb_add |
| Wdata (read) | wdata_list_tables (with sql_ref) · wdata_get_table · wdata_list_queries · wdata_run_sql · wdata_run_saved_query · wdata_list_connections |
| Wdata (write) | wdata_create_table · wdata_upload_and_import · wdata_refresh_connection |
| Graph | graph_types · graph_records · graph_edits (write) |
| Spreadsheets | spreadsheet_list_sheets · spreadsheet_ui_url · spreadsheet_update (write) |
| Anything else | workiva_request (platform / wdata / chains) |
Every API tool runs through the auto-attach mechanism: failures come back wearing the matching KB entries, resolution included.
What the KB knows
25 seeded entries, all confirmed against the live API in July 2026: 4 blockers (no API path exists — e.g. connections cannot be created programmatically), 12 gotchas (the obvious approach fails first — e.g. Wdata SQL cannot reference tables by name), and 9 nuances. Entries are dated, version-pinned, and carry the literal error strings they match.
Layout
workiva-mcp/
src/workiva_mcp/
server.py # MCP tools
kb.py # KB toolchain: parse, validate, build index, search
client.py # Workiva API client: credentials, token refresh, three hosts
promote.py # KB drafts -> branch -> PR (planned)
kb/ # the knowledge base: entries/*.md + SCHEMA.md + index.json
tests/
.githooks/ # pre-push gate: ruff + pytest + kb check
Development
One-time setup after cloning — activate the pre-push gate:
git config core.hooksPath .githooks
Every push then runs ruff, the tests, and the KB check first
(git push --no-verify bypasses in an emergency).
uv run workiva-mcp # boots the stdio server
uv run pytest # tests
uv run ruff check . # lint
uv run python -m workiva_mcp.kb check # validate entries + index currency
uv run python -m workiva_mcp.kb build # rebuild kb/index.json after editing entries
kb/index.json is generated — never edit it by hand; edit kb/entries/*.md
and rebuild.
Register with Claude Code from a clone:
claude mcp add workiva -- uv run --directory <path-to-clone> workiva-mcp
Credentials
# ~/.workiva/credentials (chmod 600)
[settings]
default_profile = sandbox
[default]
client_id = ...
client_secret = ...
[sandbox]
client_id = ...
client_secret = ...
# optional per-profile endpoint overrides:
# token_url / platform_base / wdata_base / chains_base
The file is re-read at call time, so edits — rotating a secret, switching
default_profile — take effect on the next call without restarting the
server. Profile precedence: explicit argument > WORKIVA_PROFILE >
[settings] default_profile > [default]. With no file at all,
WORKIVA_CLIENT_ID / WORKIVA_CLIENT_SECRET serve the default profile.
WORKIVA_CREDENTIALS_FILE overrides the file location.
Write safety
The server is read-only by default: tools marked WRITE (create table,
upload/import, connection refresh, …) refuse with an explanatory message and
touch nothing. Enable writes with WORKIVA_ALLOW_WRITES=1 in the server's
environment, or allow_writes = true under [settings] in
~/.workiva/credentials — the file is re-read at call time, so flipping it
takes effect immediately, and an explicit env value (even 0) always wins.
Read-only means no user-visible workspace mutations: wdata_run_sql's
internal temp-query mechanics stay allowed.
Capturing new knowledge
kb_add writes drafts to ~/.workiva/kb/drafts/ (override with
WORKIVA_KB_DRAFTS) — local, instant, no review, never part of the package.
Search reads bundled entries and your drafts, so a quirk you hit today
helps you again tomorrow, before any review happens. Drafts carry
confidence: reported and pass the same schema linter as real entries.
Promotion into the shared KB is a deliberate human act:
uv run workiva-kb list # what's waiting locally
uv run workiva-kb promote <draft-id> ... # re-stamp as confirmed, branch, commit, open PR
(--no-pr for branch+commit only, --keep-drafts to leave local copies,
--confidence to override the confirmed re-stamp.) Workspace-specific
findings simply never get promoted.
Roadmap
- [x] Scaffold: package, entry point, empty stdio server
- [x] KB data vendored: 25 entries, schema, CC-BY-4.0 license
- [x] KB toolchain: parse + validate + index build + weighted search, tests, pre-push gate
- [x] KB tools:
kb_search/kb_list/kb_get, KB packaged into the wheel - [x] Local drafts overlay +
kb_add - [x] Workiva client foundation: credential profiles in
~/.workiva/credentials, token lifecycle, three-host transport - [x] Auto-hint mechanism + read-only Wdata tools
- [x] SQL execution, saved queries, connections listing
- [x] Write gate (
WORKIVA_ALLOW_WRITES/allow_writes) + modifying Wdata tools: create table, upload → import → poll, connection refresh - [x] Graph + Spreadsheets tools (writes gated)
- [x] Escape hatch (platform / wdata / chains)
- [x]
promoteCLI: drafts → PR (workiva-kb) - [x]
v0.1.0tag,uvxinstall verified - [ ] NOTICE file — deferred until copyright ownership is settled (see the plan's open item); Apache-2.0 is complete without it
License
Code: Apache-2.0 (see LICENSE). KB entries under kb/, once landed:
CC-BY-4.0.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。