docs: add Integrations section — coding agents + frameworks#7
Merged
Conversation
New top-level Integrations sidebar covering: - Coding agents (Claude Code, OpenClaw full specs; Codex, Cursor stubs with working manual-setup blocks) - Frameworks (Vercel AI SDK, LangChain JS, Mastra, OpenAI Agents SDK, LangGraph JS — all planned stubs with intended shape) All coding-agent integrations share a common MCP server (`@atomicmemory/mcp-server`) exposing memory_search / memory_ingest / memory_package, implemented in the sibling Atomicmemory-integrations repo. Docs describe the intended install surface, config shape, and tool contracts so implementation can proceed against a fixed spec.
Docusaurus 3 requires `:::note[Title]` bracket syntax for admonition titles. The space-separated form (`:::note Planned`) was rendering the word as plain content instead of a title across all seven planned- integration stub pages.
- Replace the default Docusaurus logo.svg with logo-atomicmem.svg (the #3A60E4 icon from Atomicmem-webapp/public/icons). Also ship logo-full.svg (icon+wordmark) and logo-wordmark.svg. - Rebuild the Infima primary palette around #3A60E4 with matching dark-mode shades that mirror how the webapp lightens brand tokens. - Set body text to #1E252E (webapp primary text) and the global radius to 0.625rem to match webapp tokens. - Point the social-card reference at logo-full.svg (the previously referenced atomicmemory-social-card.png did not exist in static/img).
Match the webapp's font stack (Work Sans for display, Fira Mono for code) by loading both from Google Fonts via `stylesheets` + preconnect `headTags`. Repoint `--ifm-font-family-base` and `--ifm-font-family-monospace` at those families. Swap the favicon from the Docusaurus default ICO to `img/logo.svg` (the AtomicMem icon ported earlier) — modern browsers render SVG favicons natively.
Three review fixes: - Claude Code intro page called out `ingest / search / trust` as the tool surface while the table below it correctly listed memory_package — aligned intro to match. - OpenClaw MCP-bridge section still named `memory_trust`; swapped to memory_package. - "Tool schemas mirror the SDK surface" link pointed at /sdk/api/memory-provider (the provider authoring contract) instead of the MemoryClient request/response types. Repointed at /sdk/api/overview with an explicit callout of IngestInput / SearchRequest / PackageRequest.
Scope
- SDK V3 Scope is { user, agent, namespace, thread } — not the
{ user, workspace, agent } model the integration docs described.
- Swept workspace → namespace across claude-code.md, openclaw.md,
and mastra.md. Reflect required scope.user in install snippets.
Roadmap links (P3)
- Every planned-integration page linked to the integrations repo's
/issues page to "track progress." The repo has no issues filed,
so readers landed on an empty list. Removed those dead links and
rephrased the admonitions to explain the doc *is* the spec.
Publishing link (P3)
- The OpenClaw page pointed at `.github/workflows/publish-openclaw.yml`
which does not exist. Rephrased as "will live at" + "not yet wired
up" and kept the repo-root link as context.
I'd been leaving this untracked because the repo already commits package-lock.json and CI runs `npm ci` (see 6df76ab). Committing the pnpm lockfile on request; the repo now has both lockfiles, which can drift. Picking one lockfile and updating CI accordingly is a follow-up decision.
This repo uses npm — package-lock.json is the source of truth and .github/workflows/deploy.yml runs `npm ci`. Dropping the pnpm lockfile I added in 0134848 (ships pnpm-lock.yaml) and gitignoring it so a stray `pnpm install` cannot resurrect it and drift from the npm lockfile.
Now that the integrations repo is public, the docs can point at the actual committed files instead of hand-waving at "an intended shape." Overview - Added a Source column linking to `plugins/claude-code` and `plugins/openclaw` on the coding-agents table. - Downgraded status from `✅ Available` to `🔧 Source available` with a footnote explaining the `@atomicmemory/mcp-server` npx flow remains gated on the SDK publishing to npm. - Replaced the fictional `plugins/_template/` contributing sentence with a real "Contributing" section that links the MCP server and plugins directories and describes the actual contribution path (copy the closest plugin, swap the manifest, reuse the server). Claude Code page - Rewrote the Status callout with a specific source link and a pointer at the mcp-server status note. - Added a "View source" section linking plugin.json, SKILL.md, and the MCP server package. OpenClaw page - Same status rewrite and "View source" section (manifest, skill files, plugin entry).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@atomicmemory/mcp-server) exposingmemory_search/memory_ingest/memory_package. Implementation lives in the siblingAtomicmemory-integrationsrepo.Test plan
pnpm buildpasses locally withonBrokenLinks: 'throw'/integrations/overview