
Lightfield
- 2 repo stars
- Updated July 11, 2026
- doc2mcp/doc2mcp
lightfield is an MCP server that delivers lightfield documentation to agents through authenticated doc2mcp streamable HTTP.
About
Lightfield MCP is a Model Context Protocol server automatically produced from lightfield documentation on doc2mcp, giving developers a hosted way to let coding agents read that documentation during implementation. If you document lightfield on doc2mcp, this server is the supported path to avoid stale prompts and improvised API shapes when you work with Claude Code or similar tools. Connection uses a single streamable-http endpoint and a Bearer token treated as a password from the Connect tab—no separate doc crawler or custom RAG pipeline required for basic grounding. Use it when integrating lightfield SDKs, explaining configuration to a teammate via agent chat, or cross-checking behavior against published guides; it does not replace running tests or reading source when docs lag code. Because generation is tied to doc2mcp, refresh your docs on the platform and rely on regenerated MCP behavior rather than hand-editing tool lists. Store credentials in agent secret stores only.
- doc2mcp-generated MCP server titled lightfield with streamable-http remote hosting
- Secret Bearer token from the lightfield project Connect tab required on every MCP call
- Keeps agent answers tied to lightfield documentation you already maintain on doc2mcp
- Compatible with standard MCP remote configuration in Claude Code, Cursor, Codex, and Windsurf
- Versioned server metadata (1.0.1780875164) alongside MCP 2025-12-11 schema
Lightfield by the numbers
- Data as of Jul 12, 2026 (Skillselion catalog sync)
claude mcp add --transport http lightfield https://doc2mcp.site/api/mcp/24fd8d23-16a6-4eb9-bee0-f8080a6b31b2/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Transport | HTTP |
| Auth | Required |
| Last updated | July 11, 2026 |
| Repository | doc2mcp/doc2mcp ↗ |
What it does
Hook lightfield doc2mcp documentation into your coding agent for accurate lightfield API and product answers while you ship features.
Who is it for?
Best when you're on the lightfield project and publish docs via doc2mcp and want MCP-grounded coding assistance.
Skip if: Skip if you need live lightfield production telemetry, write operations, or docs outside the doc2mcp lightfield project.
What you get
Once lightfield MCP is registered with your Bearer token, agents can reference lightfield documentation directly during build sessions.
- MCP-linked access to lightfield documentation from your development agent
- Hosted doc2mcp remote—no local lightfield MCP server to build
- Consistent doc source between human readers and agent tool calls
By the numbers
- Remote transport: streamable-http (1 endpoint)
- Auth: 1 required secret Authorization Bearer header
- Declared server version 1.0.1780875164
README.md
doc2mcp — MCP Registry manifest
This repository is not the doc2mcp product. It is the small, GitHub‑OIDC‑authenticated publishing manifest for the official Model Context Protocol Registry.
| What | Where |
|---|---|
| MCP Registry entry | https://registry.modelcontextprotocol.io/v0.1/servers?search=doc2mcp |
| Live product | https://doc2mcp.site |
| Registry namespace | io.github.doc2mcp/doc2mcp |
| Current version | 1.0.1 |
Why a separate repo?
The MCP Registry uses GitHub OIDC to claim a namespace. Whichever GitHub
org or user runs mcp-publisher publish from a workflow gets exclusive
publishing rights to io.github.<that-org>/*.
Since we want the public, brandable namespace io.github.doc2mcp/*
(instead of io.github.gautammanak1/*), the publish workflow must run
inside the doc2mcp GitHub organization. This repository holds only
the publishing manifest and workflow — nothing else.
gautammanak1/doc2mcp → product code, Vercel deploy, docs site
doc2mcp/doc2mcp → this repo. server.json + publish workflow
What clients should use
To connect to doc2mcp from Cursor, Claude Desktop, VS Code, Windsurf,
the OpenAI Agents SDK, etc., point your MCP host at the remote URL
in server.json:
{
"type": "streamable-http",
"url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",
"headers": { "Authorization": "Bearer <your project MCP token>" }
}
Get your project_id and Bearer token from
Publishing flow
Pushing a vX.Y.Z tag to main triggers
.github/workflows/publish-mcp.yml,
which:
- Updates the
versionfield inserver.jsonto match the tag. - Installs the official
mcp-publisherCLI. - Authenticates via GitHub OIDC (
id-token: write). - Publishes the manifest to the registry.
To cut a new version:
# from this repo
git tag v1.0.2
git push origin v1.0.2
The workflow validates against the upstream JSON Schema before publish,
so a bad description length or missing required field will fail
loudly with a clear error.
License
The manifest in this repo is published under the MIT License. The doc2mcp product itself is licensed in its main repository.
Recommended MCP Servers
How it compares
Published-docs MCP endpoint, not a lightfield application runtime or infra control plane.
FAQ
Who is Lightfield MCP for?
Lightfield developers and developers who host Lightfield documentation on doc2mcp and use AI coding agents daily.
When should I use Lightfield MCP?
Use it during build and integration whenever you need the agent to follow Lightfield’s official documentation instead of general training data.
How do I add Lightfield MCP to my agent?
Get the Bearer MCP token from the Lightfield Connect tab on doc2mcp, add the listed remote URL to MCP settings, and pass Authorization Bearer with that token.