0 Fork 0

mirror of https://github.com/JackChen-me/open-multi-agent.git synced 2026-10-22 02:53:26 -05:00

Files

T

Jack Chen f0375eebea docs(examples): add Open Design MCP batch fan-out integration example (#364 )

Drive Open Design's stdio MCP server from OMA to generate N landing-page
variants in parallel via runTasks(). Each variant's async flow
(create_project, start_run, poll get_run to a terminal status) is handled
by deterministic code, not LLM polling; the worker model only drafts the
design brief. Reference-lane example alongside mcp-github and
mcp-bilig-workpaper, plus its two README index entries.

2026-07-10 22:25:22 +08:00

express-customer-support

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

with-engram

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

with-tencentdb-memory

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

with-vercel-ai-sdk

feat(ai-sdk): support Vercel AI SDK 7 (#348 )

2026-07-01 22:33:06 +08:00

mcp-bilig-workpaper.ts

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

mcp-github.ts

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

mcp-open-design.ts

docs(examples): add Open Design MCP batch fan-out integration example (#364 )

2026-07-10 22:25:22 +08:00

README.md

docs(examples): add Open Design MCP batch fan-out integration example (#364 )

2026-07-10 22:25:22 +08:00

trace-observability.ts

docs(examples): prefix example run commands with packages/core/ (#330 )

2026-06-24 17:14:23 +08:00

README.md

examples/integrations/

OMA wired to external systems: MCP servers, observability backends, other frameworks, app shells. Runnable starting points, not product docs.

Two categories live here.

Reference integrations demonstrate wiring against widely used protocols or frameworks. The OMA team maintains these once merged, regardless of who contributed them. Current:

mcp-github.ts: MCP servers via connectMCPTools().
mcp-open-design.ts: batch fan-out over an MCP server's async, long-running jobs — N Open Design landing-page variants generated in parallel via runTasks(), each variant driven create_project → start_run → poll get_run to a terminal status by deterministic code.
trace-observability.ts: the onTrace API.
with-vercel-ai-sdk/: Next.js + AI SDK + runTeam().
express-customer-support/: Express REST API + runTasks(). Contributed by @CodingBangboo via #191.

Vendor integrations show OMA paired with a specific third-party commercial product. They live under with-<product>/ and stay credited to the contributor. Current:

with-engram/: Engram memory backend. Contributed by @Agentscreator via #160.
with-tencentdb-memory/: TencentDB-Agent-Memory long-term memory (L0→L3 pipeline) via its Hermes Gateway sidecar.

Submitting a reference integration

Open a PR following the conventions in examples/README.md. For widely used protocols or frameworks, no prior discussion needed. For niche ones, open a discussion first so we can confirm the wiring is worth maintaining long-term.

Submitting a vendor integration

One condition: the integration is reciprocal. Your product's repo or docs should reference OMA as a supported integration. No payment involved, this is a signal filter for who has actually shipped against OMA.

Flow:

Open a discussion with the link to OMA in your product's docs and a sketch of the example.
Wait for a maintainer reply confirming the example is in scope.
PR it. Follow the conventions in examples/README.md.

If your product doesn't reference OMA yet, open a discussion to get listed in the Ecosystem section.

The Featured Partner program is separate and paid, for prominent README placement. Eligibility is an active OMA integration; reciprocal listing isn't required.

Out of scope here

Marketing copy for a third-party product.
Examples gated behind paid-only APIs with no free or trial tier.
Thin connectMCPTools() wrappers whose only difference from mcp-github.ts is the server name and prefix. Those belong in your own docs.