Repository navigation
Conversation
|
The following comment was made by an LLM, it may be inaccurate: |
There was a problem hiding this comment.
This is a docs-only change, so there was nothing to run. I checked the example against the v2 config schema and the current docs on latest dev. The public API is unchanged.
The main problem is which docs it targets. The example goes into packages/web/src/content/docs/mcp-servers.mdx and uses the older config shape, with the server name directly under mcp. In v2, servers go under mcp.servers. The config schema (packages/schema/src/config/mcp.ts) only allows timeout and servers under mcp, so someone using v2 who copies this example won't get the server (see the inline comment).
The v2 MCP docs now live in services/www/src/docs/content/mcp-servers.mdx. That page has no section of third-party server examples, so whether to add vendor-specific examples there is a call for the maintainers.
| { | ||
| "$schema": "https://opencode.ai/config.json", | ||
| "mcp": { | ||
| "stivio": { |
There was a problem hiding this comment.
In v2, servers go under mcp.servers (the config schema only allows timeout and servers under mcp), so this snippet won't set up the server for anyone on v2. It would need to look like "mcp": { "servers": { "stivio": { ... } } }. The v2 docs are in services/www/src/docs/content/mcp-servers.mdx, not this file.
There was a problem hiding this comment.
Thanks for the review — good catch. The example targets the docs page as it exists on dev today, using the same config shape as the other entries there. If you'd like it moved to services/www/src/docs/content/mcp-servers.mdx with the v2 mcp.servers shape (or dropped, if vendor examples don't belong in the v2 docs), happy to do that — just say the word.
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
Issue for this PR
N/A — docs addition, no linked issue.
Type of change
What does this PR do?
Adds a Stivio section to the MCP servers docs (packages/web/src/content/docs/mcp-servers.mdx). Stivio is a remote MCP server for image-to-video generation; the example shows the JSON config (Bearer auth) plus a sample prompt, following the same format as the other entries on the page.
How did you verify your code works?
Docs-only change. I verified the endpoint URL and docs link resolve, and checked the JSON snippet against the config format used elsewhere in this file. No code paths touched.
Screenshots / recordings
N/A — text-only docs change.
Checklist