Lymwave MCP server documentation
Connect an MCP-compatible client to scoped Lymwave workspace data and review-first content tools. Read tools inspect context; write tools stop at drafts and approval.
Production endpoint
https://mcp.lymwave.com/mcp- Transport
- HTTPS Streamable HTTP, stateless JSON responses
- Authentication
- OAuth for the Claude directory flow; workspace bearer tokens for custom clients
- Health check
- https://mcp.lymwave.com/health
Setup
Connect in three steps
Claude directory connections use Lymwave sign-in and a workspace consent screen automatically. The manual token steps below remain available for custom MCP clients.
Create a token
Open MCP settings, generate one token for one client, and keep the raw value in that client's secret store.
Add the server
Use https://mcp.lymwave.com/mcp with an Authorization header containing Bearer followed by the token.
Test safely
List tools, call get_workspace_context, then try a read workflow before enabling draft write scopes.
Generic HTTP configuration
URL: https://mcp.lymwave.com/mcp
Authorization: Bearer <workspace-token>Do not place the token in the URL, source control, prompts, or article content. Client-specific guides are available for Claude Code, Codex, and Cursor.
Read capabilities
- • Workspace and publishing context
- • Article plans, full articles, and quota
- • Internal-link targets and content paths
- • Markdown validation and SEO/AEO/GEO review
Write capabilities
- • Create a text-only article draft
- • Update an existing unpublished draft
- • Submit a draft for approval without publishing
Data and safety boundaries
Tokens are scoped to one workspace and can be revoked. Lymwave records minimized operational metadata for security and reliability, not raw tokens, prompts, article bodies, Markdown, or HTML. Draft generation sends only the requested workflow context to configured AI providers. Customer content is not used to train shared AI systems.
Example prompts
- Show the next five article plans and the remaining article quota.
- Review this draft for SEO, AEO, and GEO issues, then list the highest-priority fixes.
- Suggest safe internal-link targets and a repository path for this article.
- Update this draft and submit it for approval, but do not publish it.
Troubleshooting
401 Unauthorized
Confirm the Authorization header, token expiry, workspace, scopes, and revocation state.
No resources listed
Expected: Lymwave exposes MCP tools, not resources or resource templates.
Tool permission error
Regenerate a token with the necessary least-privilege read or draft scope.
Connection failure
Check the health URL, HTTPS endpoint, JSON content type, and whether a network policy blocks the server.
Frequently asked questions
What is the Lymwave MCP server?
It is Lymwave's first-party remote Model Context Protocol server for scoped content planning, draft, validation, and publishing-preparation workflows.
Can an MCP tool publish or delete content?
No. The public MCP surface can create and update drafts or submit them for approval, but direct publish and delete tools are intentionally unavailable.
Does MCP draft creation generate images?
No. MCP-created drafts are text-only and do not trigger Lymwave's featured-image generation workflow.
Is Lymwave listed in the Claude Connector Directory?
Not yet. Lymwave works with supported custom MCP clients today. Directory availability will be stated only after Anthropic review and approval.