Connect Finta MCP to goose on Linux

Direct answer: On Linux, install the current goose CLI, run goose configure, add a Remote Extension (Streamable HTTP) named Finta, and use https://finta.ai/mcp as the endpoint. Complete Finta OAuth, select the intended organization, then verify one read-only CRM request before enabling broader tools.

The goose project was founded by Block and is now stewarded by the Agentic AI Foundation at the Linux Foundation. Use the current aaif-goose/goose repository, not an old Block repository or stale install URL.

Before you connect

Check	Recommended state
Finta	You can sign in and access the intended organization.
goose	Current Linux CLI or Desktop build from the AAIF project.
Model provider	Configured and working before adding Finta.
Transport	Remote Extension using Streamable HTTP.
Permission mode	Reviewed before Finta data or tools are exposed.

goose warns that it operates autonomously by default. Its Developer extension can run commands and modify local files. Review goose permission mode and tool permissions before connecting sensitive relationship or capital-workflow data.

Install goose on Linux

The current goose quickstart provides this CLI installer:

curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | bash

Review the script and your organization's software-install policy before running a command fetched from the internet. If you prefer the desktop app on Debian or Ubuntu, follow the current goose quickstart for the DEB package.

After installation, configure a model provider before testing extensions:

goose configure

Add Finta as a persistent remote extension

Run goose configure.
Select Add Extension.
Choose Remote Extension (Streamable HTTP).
Name the extension Finta.
Enter https://finta.ai/mcp as the remote URL.
Keep a conservative timeout during initial testing.
Save and enable the extension.
Complete the Finta authorization flow when goose opens or prints the sign-in URL.
Select the Finta organization you intend to use and review the requested access.
Start a new goose session if the current session does not refresh the tool inventory.

The current goose extension guide documents the Remote Extension (Streamable HTTP) option. It also says OAuth-protected remote extensions normally obtain a client identity automatically through a Client ID Metadata Document or Dynamic Client Registration. Do not add a static client secret or paste a Finta token into the configuration unless Finta documentation specifically requires it.

Test Finta for one session instead

For a temporary session, the current goose CLI also supports:

goose session --with-streamable-http-extension "https://finta.ai/mcp"

This starts a session with the remote extension but does not install it as a persistent default. Use the configuration flow above when you want Finta available in future sessions.

Add Finta in goose Desktop

Open the sidebar.
Select Extensions.
Choose Add custom extension.
Select the remote Streamable HTTP type.
Use Finta as the name and https://finta.ai/mcp as the URL.
Save, complete Finta authorization, and keep the extension disabled until you are ready to run a controlled test.

The exact field labels can change between desktop releases. Use the official extension guide as the source of truth.

Verify the connection without changing data

Start a new session and use this prompt:

List the Finta tools available in this session. Then search my Finta CRM for a contact I name. Do not create, update, send, schedule, enroll, archive, delete, or run a shell command.

Inspect the tool name, arguments, and target organization. A successful tool listing confirms discovery. A successful read confirms that the authorized account can access at least that query. Neither proves that all Finta tools, records, or external connections are available.

Use Finta for grounded relationship work

The useful pattern is to ask goose for a small, reviewable relationship decision:

Retrieve a CRM record before preparing for a meeting.
Summarize recent available context and open commitments.
Identify possible relationship paths while keeping consent unknown unless it is documented.
Draft a next step and stop before an external send.

Aurora keeps available workspace and supported-connection context together, shows source and tool receipts, and makes supported confirmation boundaries explicit. Finta remains the organization-scoped system of record. goose remains the client deciding when to invoke a discovered tool.

Permission checklist for goose

Review and enable only the Finta tools needed for the task.
Use goose permission mode and tool permissions to require review where appropriate.
Keep high-impact Developer tools separate from a relationship-data test.
Do not let content retrieved from an untrusted source instruct goose to invoke Finta tools.
Confirm the selected Finta organization before any write.
Revoke the Finta connection if the Linux account, device, or workspace changes hands.

Troubleshooting

Problem	What to check
`goose` is not found	Confirm the installer completed and the goose binary directory is on `PATH`.
The remote extension will not save	Choose Remote Extension (Streamable HTTP) and use exactly `https://finta.ai/mcp`.
OAuth does not open	Run the configuration from an interactive terminal and inspect the printed authorization URL.
OAuth finishes but tools do not appear	Start a new session, confirm the extension is enabled, and refresh the extension state.
The wrong CRM records appear	Confirm which Finta organization was selected during authorization.
A tool runs without the review you expected	Stop the session and tighten goose permission mode and tool permissions before continuing.
A write is blocked	Read the Finta permission, validation, confirmation, or credit response. Do not retry it in a loop.

For more diagnostics, use Troubleshoot a Finta MCP Connection.

Limitations

The AAIF goose project changes quickly, so menu labels and configuration behavior can move between releases.
goose Desktop and CLI can refresh extensions differently. A new session may be required.
goose's broad local capabilities increase the impact of a malicious prompt or mistaken instruction.
A connected extension does not grant access beyond the authorized Finta organization.
Finta results can be incomplete when CRM records or supported source connections are incomplete.
Relationship evidence does not establish consent, endorsement, investor interest, or a promised outcome.

Frequently asked questions

Is goose still a Block product?

The project was founded by Block. Its current governance says it is now stewarded by the Agentic AI Foundation and established as a Linux Foundation project. Current code and documentation live under aaif-goose/goose.

Which transport should I choose for Finta?

Choose Remote Extension (Streamable HTTP) and use https://finta.ai/mcp.

Do I need to paste an OAuth token into goose?

No. Complete the browser-based Finta authorization flow. Do not place a Finta password or token in a prompt, repository, or shared configuration file.

Can I use the Finta extension for only one session?

Yes. Use goose session --with-streamable-http-extension "https://finta.ai/mcp". Persistent use should go through goose configure or the Desktop extensions interface.

Related guides

Verification status: Current AAIF goose Linux install, remote Streamable HTTP extension, OAuth, and security documentation plus the linked live Finta routes were verified August 21, 2026. An authenticated goose-to-Finta connection, discovered-tool inventory, and read-only Finta tool-call receipt remain pending.

Explore Aurora and connect Finta