Lymwave logo

MCP server

Use Lymwave with VS Code and MCP-compatible assistants

Bring Lymwave workspace context, article plans, article retrieval, quota checks, draft workflows, internal links, markdown validation, and SEO/AEO/GEO review into VS Code environments that support MCP-compatible assistants.

Lymwave MCP server

15 tools available

Use the production MCP endpoint with a workspace bearer token. Tools support workspace context, publishing context, article plans, article retrieval, quota checks, draft creation and updates, approval submission, internal-link targets, path suggestions, markdown validation, SEO/AEO/GEO review, and setup instructions. Direct publishing and delete tools are intentionally unavailable.

https://mcp.lymwave.com/mcp
get_workspace_contextget_publishing_contextget_article_planlist_article_plansget_articleget_article_creation_requirementsget_article_quotacreate_article_draftupdate_article_draftsubmit_article_for_approvallist_internal_link_targetsuggest_content_file_pathvalidate_markdown_articlereview_content_for_seo_aeo_geoget_mcp_integration_instructions

Workflow

Review-first content work from VS Code

The Lymwave MCP server is useful when content files, metadata, and publishing paths live near code. It helps AI assistants fetch the right context before suggesting content changes.

1

Connect an MCP-compatible VS Code assistant to https://mcp.lymwave.com/mcp with a workspace bearer token.

2

Ask for workspace context, publishing paths, article plans, article quota, draft workflows, validation, review, or internal-link targets.

3

Validate markdown and review drafts for SEO, AEO, and GEO before committing content changes.

4

Keep publishing controlled by Git, CMS, or the Lymwave dashboard.

Context

Read workspace, publishing, article plan, article retrieval, and quota context before editing.

Drafts

Create, update, validate, and submit review-ready article drafts without direct publishing.

Review

Use markdown validation and SEO/AEO/GEO review tools before committing changes.

FAQ

VS Code MCP workflow questions

Is this an official Microsoft or VS Code integration?

No. This page describes a workflow for VS Code environments and MCP-compatible AI assistants. It does not claim an official Microsoft or VS Code partnership.

What endpoint should VS Code MCP clients use?

Use the production Lymwave MCP endpoint at https://mcp.lymwave.com/mcp with a workspace-scoped bearer token.

Do public MCP tools publish content directly?

No direct publish or delete MCP tools are exposed. The MCP workflow is designed for context, drafts, validation, review, and approval-oriented content preparation.