Hosted MCP server/Finance

Terminal Tax MCP server

Hosted at mcp.terminal.tax·Streamable HTTP

Terminal Tax e-files a 2025 US federal Form 1040 from an AI assistant, with the taxpayer reviewing and signing on one hosted page. The provider's integration guide documents a raw JSON-RPC create_filing_session flow and states that nothing should be installed or connected and the server need not be in the tool list. Registering the MCP endpoint is optional, not the documented path.

mcp.terminal.tax Streamable HTTP No authentication Server not checked yet Reviewed 2026-11-16
About

Where it fits

Taxpayers and filers preparing a 2025 US federal Form 1040 with an assistant and a hosted review step.

  • Read the provider's create_filing_session flow.
  • Create a filing session for a 2025 Form 1040.
  • Review and sign on the hosted page.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Optional MCP registration

Terminal Tax says nothing needs to be installed or connected and the server need not be in the tool list. The documented flow is a raw JSON-RPC create_filing_session call. Registering the endpoint below is optional.

  1. Read the provider's integration flow

    Terminal Tax documents a raw JSON-RPC create_filing_session call; no install is required and the server need not appear in the client tool list.

  2. Create a filing session

    Follow the provider's JSON-RPC example for create_filing_session and send the taxpayer to the hosted review and signature page.

  3. Optional: register the endpoint

    If your client benefits from a registered server, add https://mcp.terminal.tax/v1/hosted-mcp; the provider treats this as optional.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.terminal.tax/v1/hosted-mcp
Host
mcp.terminal.tax · /v1/hosted-mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
terminal-tax
Listing type
Community or directory listing

The installer uses the server name terminal-tax. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that terminal-tax appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Read the provider's create_filing_session flow. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Terminal Tax documentationhttps://terminal.tax/integrationsGitHub repositoryhttps://github.com/terminaltax/agent-tax-filing-handoff