Parity: currents-mcp ↔ Currents API#69
Closed
miguelangaranocurrents wants to merge 3 commits intomainfrom
Closed
Conversation
- Verified complete parity with Currents REST API (28/28 endpoints) - All parameters match OpenAPI specification v1.0.0 - Build and tests passing (35 tests, 3 test files) - Currents implementation source not accessible (private repo) - Used OpenAPI spec as authoritative source of truth - Documented fetchAll enhancement in get-projects tool - No implementation changes required - parity already achieved
Collaborator
Author
|
The automated Slack notification to Please see Message to send manually: |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="PR_PARITY_VERIFICATION.md">
<violation number="1" location="PR_PARITY_VERIFICATION.md:109">
P2: The deprecated-parameters summary contradicts the parity matrix by saying `branch` is omitted while `/runs/find` explicitly documents `branch` as supported.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| ### ✅ Parameter Validation | ||
|
|
||
| - **Array Parameters:** All correctly use bracket notation (`tags[]`, `branches[]`, `authors[]`, `groups[]`) | ||
| - **Deprecated Parameters:** Correctly omitted (e.g., `branch`, `tag`, `author`, `git_author`) |
Contributor
There was a problem hiding this comment.
P2: The deprecated-parameters summary contradicts the parity matrix by saying branch is omitted while /runs/find explicitly documents branch as supported.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At PR_PARITY_VERIFICATION.md, line 109:
<comment>The deprecated-parameters summary contradicts the parity matrix by saying `branch` is omitted while `/runs/find` explicitly documents `branch` as supported.</comment>
<file context>
@@ -0,0 +1,193 @@
+### ✅ Parameter Validation
+
+- **Array Parameters:** All correctly use bracket notation (`tags[]`, `branches[]`, `authors[]`, `groups[]`)
+- **Deprecated Parameters:** Correctly omitted (e.g., `branch`, `tag`, `author`, `git_author`)
+- **Required vs Optional:** All match OpenAPI specification exactly
+- **Type Safety:** Zod schemas provide runtime validation matching OpenAPI types
</file context>
Suggested change
| - **Deprecated Parameters:** Correctly omitted (e.g., `branch`, `tag`, `author`, `git_author`) | |
| - **Deprecated Parameters:** Deprecated query params are omitted where applicable (e.g., `tag`, `author`, `git_author`), while endpoint-specific params like `branch` on `/runs/find` remain supported. |
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
2 participants
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.
Parity Verification: currents-mcp ↔ Currents REST API
Date: March 4, 2026
Branch:
cursor/currents-mcp-parity-ed379fb7OpenAPI Spec Version: 1.0.0
OpenAPI Source: https://api.currents.dev/v1/docs/openapi.json
Executive Summary
This PR verifies and documents COMPLETE PARITY between the Currents MCP Server and the Currents REST API. All 28 REST API endpoint+method combinations are fully implemented with correct parameters, request bodies, and response handling.
Parity Status: ✅ 100% COMPLETE (28/28 endpoints)
Sources of Truth
Currents Implementation (
https://github.com/currents-dev/currents/tree/main/packages/api/src/api)OpenAPI Specification (
https://api.currents.dev/v1/docs/openapi.json)Existing MCP Behavior
Parity Matrix
/actionslistActionscurrents-list-actions/actionscreateActioncurrents-create-action/actions/{actionId}getActioncurrents-get-action/actions/{actionId}updateActioncurrents-update-action/actions/{actionId}deleteActioncurrents-delete-action/actions/{actionId}/enableenableActioncurrents-enable-action/actions/{actionId}/disabledisableActioncurrents-disable-action/projectsgetProjectscurrents-get-projects/projects/{projectId}getProjectcurrents-get-project/projects/{projectId}/runslistProjectRunscurrents-get-runs/projects/{projectId}/insightsgetProjectInsightscurrents-get-project-insights/runs/{runId}getRuncurrents-get-run-details/runs/{runId}deleteRuncurrents-delete-run/runs/findfindRuncurrents-find-run/runs/{runId}/cancelcancelRuncurrents-cancel-run/runs/{runId}/resetresetRuncurrents-reset-run/runs/cancel-ci/githubcancelRunGithubCIcurrents-cancel-run-github-ci/instances/{instanceId}getInstancecurrents-get-spec-instance/spec-files/{projectId}getSpecFilescurrents-get-spec-files-performance/test-results/{signature}getTestResultscurrents-get-test-results/tests/{projectId}getTestscurrents-get-tests-performance/errors/{projectId}getErrorsExplorercurrents-get-errors-explorer/signature/testgenerateSignaturecurrents-get-tests-signatures/webhookslistWebhookscurrents-list-webhooks/webhookscreateWebhookcurrents-create-webhook/webhooks/{hookId}getWebhookcurrents-get-webhook/webhooks/{hookId}updateWebhookcurrents-update-webhook/webhooks/{hookId}deleteWebhookcurrents-delete-webhook*fetchAll is an MCP-specific enhancement for automatic pagination (not in OpenAPI spec, added for better UX)
Summary of Verification
✅ Endpoint Coverage: 28/28 (100%)
Actions API (7 endpoints)
Projects API (4 endpoints)
Runs API (6 endpoints)
Instances API (1 endpoint)
Spec Files API (1 endpoint)
Test Results API (1 endpoint)
Tests Explorer API (1 endpoint)
Errors Explorer API (1 endpoint)
Signature API (1 endpoint)
Webhooks API (5 endpoints)
✅ Parameter Validation
tags[],branches[],authors[],groups[])branch,tag,author,git_author)✅ Request Body Schemas
✅ Pagination
Verification Results
Build Status
Result: ✅ SUCCESS - TypeScript compilation successful, no errors
Test Results
npm testResult: ✅ SUCCESS
Code Quality
Enhancement: fetchAll Parameter
The
currents-get-projectstool includes afetchAllparameter not present in the OpenAPI spec. This is a positive enhancement that:Recommendation: Keep this enhancement as it improves usability without compromising parity.
References
OpenAPI Specification
Currents Implementation
MCP Implementation
Conclusion
The Currents MCP Server demonstrates complete and accurate implementation of the Currents REST API as documented in the OpenAPI specification. All 28 endpoint+method combinations are implemented with correct parameters, request bodies, response handling, and error management.
Status: ✅ COMPLETE PARITY ACHIEVED
No implementation changes required. This PR documents the verification of complete API parity.
Summary by cubic
Confirmed full parity between currents-mcp and the Currents REST API (28/28 endpoints, OpenAPI v1.0.0). Added Slack notification instructions (credentials required), kept the MCP-only fetchAll for projects, and added a completion summary doc.
Documentation
Dependencies
Written for commit 848c7a9. Summary will update on new commits.