Skip to content

docs(coinbase-mcp): explain how to fund a perpetuals (INTX) portfolio with coinbase_transfer - #22

Open
barmstrong wants to merge 1 commit into
coinbase:mainfrom
barmstrong:docs/coinbase-mcp-fund-perps-portfolio
Open

barmstrong wants to merge 1 commit into
coinbase:mainfrom
barmstrong:docs/coinbase-mcp-fund-perps-portfolio

Conversation

@barmstrong

Copy link
Copy Markdown

Description

Agents can't work out how to fund collateral for perpetual futures. The collateral lives in the portfolio of type INTX and must be USDC, so a USD holder converts first, and the transfer settles asynchronously.

This adds a "Fund a perpetuals (Global Derivatives) portfolio" section to the coinbase-mcp portfolios reference. The section covers:

  • finding the INTX portfolio
  • converting USD to USDC when needed
  • transferring once
  • verifying with coinbase_portfolios_get
  • never resubmitting
  • handling an amount-limit refusal
  • why dated futures need no transfer

It also lists INTX as a portfolio_type filter value and updates the Portfolios row in SKILL.md. The guidance matches the coinbase_transfer tool description on the server.

@ethanoroshiba, could you check that this is correct before it merges?

Change type

  • Harness integration or metadata
  • Skill workflow
  • Bug fix
  • Documentation
  • Breaking change (describe migration)

Validation

  • python3 -m unittest discover -s tests: 38 tests, OK.

  • python3 scripts/build-distributions.py: ran without errors.

  • Not run: native harness loading and OAuth checks. This change only edits skill text.

  • Generated portable manifest and MCP config validate against the vendored Agent Plugins schemas

  • Package paths and skill references remain inside each generated plugin root

  • Marketplace, skills, MCP, and icon paths are valid

  • Exactly one canonical skill library; generated copies are not committed

  • Claude compatibility metadata/endpoint and marketplace sources agree with the portable package

  • Tool schemas, authorization, and retry behavior reviewed

  • README and changelog updated; versions consistent

  • No unapproved disclosures or sensitive data

  • Signed commits

Release considerations

Needs review from a coinbase-mcp maintainer before merging. No version bump; this is in the unreleased 0.0.2 entry.

@cb-heimdall

cb-heimdall commented Nov 13, 2026 •

Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
1 if authored by an app that is not allowlisted and lacks verified human attribution 0
Sum 2

⚠️ Ignored Reviews (1)

Reviewer Reason
ethanoroshiba Soft review, as user does not have write permissions

@cb-heimdall

Copy link
Copy Markdown

Review Error for ethanoroshiba @ 2026-11-13 22:25:10 UTC
User failed mfa authentication, see go/mfa-help

@cb-heimdall

Copy link
Copy Markdown

Review Error for jazz-cb @ 2026-11-13 22:37:20 UTC
User failed mfa authentication, either user does not exist or public email is not set on your github profile. \ see go/mfa-help

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants