Wrapper Mcp
Expose the same Czech NLP and PII toolkit through a thin MCP wrapper when your agent config expects the wrapper-mcp package layout.
Overview
wrapper-mcp is a MCP server for the Ship phase that wraps Czech NLP and PII anonymization tools (35-language NER, 80+ PII types) for agent clients.
What is this MCP server?
- MCP wrapper (version 0.8.5) around Czech NLP capabilities: NER, anonymize, morphology, translation, spellcheck
- Same advertised scope: 35-language NER and 80+ PII anonymization patterns
- PyPI stdio transport via identifier wrapper-mcp
- Use when downstream tooling or docs reference wrapper-mcp instead of anonymize-mcp directly
- Keeps agent integrations consistent if you standardize on the wrapper package name
- MCP schema version 0.8.5 for wrapper-mcp
- Advertised 35-language NER and 80+ PII anonymization scope matches sibling server description
- PyPI registry type with stdio transport
What problem does it solve?
Your agent setup may reference wrapper-mcp while the actual redaction power lives in a sibling package, causing confusion about which MCP entry to register.
Who is it for?
Builders already standardized on the wrapper-mcp PyPI name who need Czech and multilingual PII handling in MCP workflows.
Skip if: Users who only need anonymize-mcp and want to avoid maintaining two nearly identical MCP servers.
What do I get? / Deliverables
After you add wrapper-mcp over stdio, agents can call the documented NLP and anonymization surface through one consistent package identifier.
- Single MCP entry point named wrapper-mcp for Czech NLP and anonymization calls
- Aligned agent toolchain when docs reference the wrapper package
- Redacted or entity-tagged text ready for safer sharing workflows
Recommended MCP Servers
Journey fit
Wrapper servers still serve ship-time safety goals—sanitizing text before it crosses trust boundaries—even if the implementation is packaging glue around core NLP tools. Security shelf fits because the underlying capabilities are anonymization and NER for data leaving your dev environment, not greenfield feature coding.
How it compares
Packaging wrapper MCP server around the same Czech NLP stack, not a distinct redaction engine from scratch.
Common Questions / FAQ
Who is wrapper-mcp for?
It is for agent operators whose MCP configuration or monorepo expects the wrapper-mcp package while still needing Czech NLP and PII tools.
When should I use wrapper-mcp?
Use it when ship or operate sanitization workflows are wired to wrapper-mcp specifically, or when your template lists that identifier instead of anonymize-mcp.
How do I add wrapper-mcp to my agent?
Register the PyPI MCP server wrapper-mcp with stdio transport in your client, install dependencies for version 0.8.5, and disable duplicate NLP servers if both wrapper and anonymize entries are present.