Skip to navigation

Develop a Tool locally

Develop a Git-backed Tool on your computer with the Method extension and Method Tool MCP. The extension can sign you in, configure Git authentication for the Tool repository, clone it, and prepare the local MCP server. This workflow uses a Tool repository; Developer MCP is a separate hosted connection for external MCP clients.

Local development is especially useful for Tools that use compiled artifacts. You can complete the compilation process locally, test the artifact, and then upload it with Method Tool MCP. This keeps the build-and-iterate loop in your editor before you publish a Tool version.

Prerequisites

You need:

  • Access to a Method instance with Open locally enabled for your Tool
  • An editable, user-managed Tool repository, created or forked in Method
  • Git and VS Code or Cursor installed on your computer
  • Permission to sign in to the same Method instance that hosts the Tool

If you have not created a Tool yet, start with Create and publish a Tool. A repository fork preserves its Git history; a fork of a legacy published Tool starts a new repository from its definition and code.

Open the Tool in your editor

  1. Open the Tool detail page in Method and select Open locally.
  2. Under First time? Install the Method extension, download the .vsix file. Install it in your editor’s Extensions panel and reload the editor if prompted. The extension includes Method Tool MCP, so the editor flow needs no separate MCP download.
  3. Select Open in VS Code or Open in Cursor. Allow your browser to open the editor, then approve Open locally in the editor.
  4. Choose a parent folder for the clone and complete browser sign-in if prompted. The extension configures Git authentication for this repository, clones the Tool, adds local editor configuration, and opens the folder. If the editor reports that the current workspace is untrusted, trust it and open the Tool link again.
Method Open in your editor dialog showing the extension download, Open in Cursor and Open in VS Code links, MCP instructions, and terminal and manual setup sections
The Open in your editor dialog provides the extension, editor links, and MCP setup steps.

The repository URL should be the exact HTTPS clone URL shown by this Tool’s dialog. Keep credentials out of the URL and repository files.

Enable Method Tool MCP

After cloning, start the method-tool MCP server:

  • VS Code: Run MCP: List Servers from the Command Palette, select method-tool, and start it. Approve the prompt if one appears.
  • Cursor: Open Settings → MCP and enable method-tool.

Start a new agent chat after the server connects. The MCP configuration is local to the Tool workspace and points to the Method instance used for the clone.

Set up from a terminal

For terminal setup, install method-tool-mcp on your PATH, then copy the API URL and clone URL from Open locally. In a macOS or Linux shell, run:

API_URL="https://<instance-host>/method/api"
CLONE_URL="<exact-HTTPS-clone-URL-from-Open-locally>"
METHOD_API_BASE_URL="$API_URL" method-tool-mcp login
method-tool-mcp git-setup --api-url "$API_URL" --clone-url "$CLONE_URL"
git clone "$CLONE_URL"

Use the exact URLs from the same Method instance. git-setup configures Git for that repository URL. The helper uses your Method login to obtain and renew a repository-scoped Git credential. If you use Manual Git credentials instead, the password expires after four hours and must be replaced.

The extension’s bundled MCP binary may not be on your shell’s PATH. If command -v method-tool-mcp returns nothing, use the editor commands above or install the CLI on your PATH. The editor can use its bundled binary without a shell installation.

For a repository created before local setup files were added, use Manual MCP configuration in the dialog to copy .vscode/mcp.json and .method/development.json. Check existing files before replacing them.

Verify the setup

  1. Confirm the checkout contains tool.json and run git remote get-url origin. The remote should match the HTTPS clone URL from Method, without embedded credentials.
  2. Confirm Method: Sign In completes in the editor.
  3. Confirm method-tool is running in MCP: List Servers in VS Code or Settings → MCP in Cursor.
  4. Run git fetch in the Tool checkout to check repository authentication.

Local edits and MCP validation do not publish a Tool version. Follow Create and publish a Tool when you are ready to validate, release, and test the Tool.

Troubleshooting

SymptomWhat to do
Your browser did not open VS Code or Cursor, or you dismissed the editor’s Open locally promptOn the Tool page, select Open locally and choose Open in VS Code or Open in Cursor again. Allow the browser to open the editor, then approve Open locally in the editor.
Sign-in was dismissed, expired, or targeted the wrong instanceRun Method: Sign In from the editor’s Command Palette. Check the Method API URL in editor settings, complete browser login, then retry.
Clone, fetch, or push reports an authentication errorRun Method: Configure Git Authentication and paste the exact clone URL from the Tool’s Open locally dialog. Approve setup, run Method: Sign In if needed, then retry Git.
method-tool-mcp: command not found in a terminalThe extension’s bundled binary is not necessarily on your shell’s PATH. Use the editor flow, or install the CLI on your PATH before running terminal commands.
Method commands are absent from the Command PaletteConfirm the Method extension is installed and enabled in the current editor profile, then reload the editor.
Local tooling refuses an untrusted workspaceTrust the Tool workspace in the editor, then retry the Method command.
The chosen clone folder already existsChoose another parent folder. To continue in an existing checkout, open it in the editor and confirm its origin matches the Tool’s clone URL.
method-tool does not appear or startConfirm the Tool folder is open as a trusted workspace. Check its MCP configuration and the extension installation, then restart the MCP server.
Open locally is missing or no clone URL appearsConfirm that the Tool is an editable Git-backed repository and that local development is enabled on the Method instance. Ask your Method administrator if access is still unavailable.

If a release fails after a commit or push, inspect the release status before retrying. The commit or tag may already exist even though publication did not complete.