Add the TabComposer server

Check that your assistant can connect

TabComposer works with assistants that can connect to a remote MCP server over HTTP and complete browser sign in. In your assistant's settings, look for a choice such as Connectors, Integrations, or MCP servers. The name and location vary between assistants.

Choose a remote server connection. A setup that only asks you to run a local command is a different connection type and cannot use the hosted TabComposer server address below.

Add the TabComposer server

In your assistant's settings, add a remote MCP server. If it asks for a display name, enter TabComposer. Paste this production server address exactly:

Save the connection or choose Connect. Your assistant should then ask you to sign in to TabComposer. Button names and the order of these steps can differ between assistants.

Sign in and approve access

The sign in and approval flow is hosted at https://app.tabcomposer.com/oauth/consent. Start it from your assistant and let it open the browser; opening the address on its own may not start a connection.

In the browser, sign in to the TabComposer account that holds the songs you want to read. Check the assistant named on the approval screen and review the access it requests before you approve it. Then return to your assistant to finish connecting.

If the browser is signed in to the wrong TabComposer account, switch to the account with the right library and start sign in again from your assistant.

Try a first request

Once the connection is ready, ask your assistant to find music in your library. Try requests such as these:

The list includes song titles and details such as instrument, tuning, time signature, tempo, capo, and last update time. To open a complete score, the assistant uses get_tab with the tab's UUID. If you only know a title, ask it to find the matching tab first. A tab's full score is included by default; the assistant can also request just its details.

A list shows 20 tabs by default and can show up to 100 at a time. If your library is larger, ask the assistant to search more narrowly or continue to the next results.

• List my tabs.
• Find my acoustic guitar tabs.
• Find tabs updated since last month.
• Look for a tab called [song title] and read its full score.

Create, validate, and edit tabs

Ask your assistant to create a blank tab with the song details you want, or provide a complete score. If you do not provide a score, the blank tab starts as Untitled song, Acoustic Guitar, 4/4 at 96 BPM, with capo 0, six standard strings, and one empty Verse bar unless you choose other details.

Before creating a tab from a complete score, ask your assistant to validate it. Validation checks the required song details and that the score's sections cover its bars. It reports errors and warnings without saving or changing a tab, and it needs the complete score.

To edit a tab, ask your assistant to read it first, then describe the change. Changes to song details such as title or tempo leave the score alone; sending a replacement score replaces the whole score. If the tab changed since it was read, TabComposer rejects the update rather than overwriting the newer version. Ask the assistant to read the current tab and retry. A tuning change requires the complete score and a string list that matches the new tuning.

• Create a blank tab called [song title] for acoustic guitar in 4/4 at 96 BPM.
• Validate this complete score and show me any errors before creating it: [score].
• Read [song title] and change its tempo to 112 BPM.
• Read [song title], then replace its score with this complete version: [score].

Know what you are sharing

The server provides five tools: list_tabs searches your library, get_tab reads a tab, validate_tab checks a complete score without saving it, create_tab saves a new blank or complete tab, and update_tab changes an existing tab. It does not provide tools to copy, duplicate, or delete tabs.

An assistant can only access tabs in the library of the player who signed in and approved it. It cannot read another player's library. If a tab is unavailable, the response does not reveal whether it belongs to someone else.

If the connection does not work

Check that you added the exact production server address above as a remote MCP server, not as a local command. Your assistant must support remote MCP connections and OAuth sign in in a browser; the setup screens and labels differ by assistant.

If sign in did not finish, start the connection again from your assistant, complete the TabComposer approval in the browser, and return to the assistant. Make sure the browser is signed in to the account whose library you expect to read.

If a song is missing, ask the assistant to search by its exact title or filter by instrument, and check that you connected the account that owns it. If you have many tabs, ask it to continue through the results.

If validation reports errors or warnings, ask the assistant to show them, revise the complete score, and validate it again. If an update is rejected because the tab changed, ask the assistant to read the latest version and reapply your change.