Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Issue with JWT and metadata deployment

Open
#10 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active

Research direction

Start with the sf-mcp-server:sf-deploy-metadata entry point and reproduce the deployment using the JWT-based credentials described in the issue. Trace whether the tool exposes or selects a SOAP versus REST transport; done means metadata deployment works with this authentication setup or the limitation and supported configuration are clearly documented.

Written by the indexing model from the issue text.

Description

Hi, I was making some tests and was unable to deploy metadata using the mcp.

sf-mcp-server:sf-deploy-metadata (MCP)(usernameOrAlias: "coe", directory: "/workspace/account-field-project", manifest: "/workspace/account-field-project/package.xml")
⎿ Error: Failed to deploy metadata: SOAP API does not support JWT-based access tokens. You must disable the "Issue JSON Web Token (JWT)-based access tokens" setting in your Connected App or External Client App

Is there anyway to force rest api to be used, not sure why it is calling soap api.

Best Regards,

Dominant language
No language data
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/mcp

All issues in forcedotcom/mcp

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.