feat: add Xquik registry entry#2
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 913df7b8c4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| displayName: Xquik | ||
| description: X automation API for search, extraction, compose, events, monitors, and webhooks | ||
| specUrl: https://xquik.com/openapi.json | ||
| baseUrl: https://xquik.com |
There was a problem hiding this comment.
When users run toolcast add xquik, src/cli.ts always emits toolcast serve <specUrl> --base-url <entry.baseUrl>, so this value overrides the OpenAPI server. The Xquik spec declares https://xquik.com/api/v1 and paths like /account; with https://xquik.com here, generated tools call URLs such as https://xquik.com/account instead of https://xquik.com/api/v1/account, making the generated MCP config hit the wrong routes.
Useful? React with 👍 / 👎.
| specUrl: https://xquik.com/openapi.json | ||
| baseUrl: https://xquik.com | ||
| authType: apiKey | ||
| authEnvVar: XQUIK_API_KEY |
There was a problem hiding this comment.
For the toolcast add xquik path, this env var is the only credential written into .mcp.json, but the server does not use registry metadata when serving; for API-key schemes resolveAuth only reads API_KEY or the header-derived X_API_KEY from the spec's x-api-key scheme. If users follow the generated config and set only XQUIK_API_KEY, no x-api-key header is sent and authenticated Xquik endpoints return 401.
Useful? React with 👍 / 👎.
kriptoburak
force-pushed
the
codex/add-xquik-registry-entry
branch
from
913df7b to
0caa59e
Compare
|
Updated the registry entry in
Validation:
|
1 participant
Summary
Validation
npm test registrynpm run buildnpm run lint