Backbone

io.back-bonePublished by back-bone.ioOfficial publisherv1.0.0Updated Oct 29, 2026

Manage your back office: invoices, reminders, receipts and time tracking in Germany and Austria.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Backbone that lets an assistant manage back-office work such as invoices, payment reminders, receipts and time tracking in Germany and…

What you can do
  • Manage invoices, payment reminders and receipts in the back office
  • Track and handle time tracking entries
  • Work with German and Austrian back-office records through the connected account
  • Tool-level details are not published, so the exact actions available are only visible after connecting
When to use it
Useful for freelancers, small businesses or teams in Germany and Austria who already run their back office in Backbone and want an assistant to handle invoices, reminders, receipts and time tracking without switching apps.
Requirements
A remote endpoint at back-bone.io reached over streamable HTTP; OAuth sign-in to a Backbone account is required. No environment variables or headers are declared.
Before you install
The server works on financial back-office records, so expect actions that create, change or send invoices, reminders and receipts. OAuth grants access to your Backbone account; review the scopes before authorizing. No tool list is published, so confirm what it can write before use.

Installation

In SourceWeft

  1. Open Backbone in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.back-bone%2Fbackbone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "backbone": {
      "type": "http",
      "url": "https://back-bone.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.