AppStruct Docs

npx add-mcp 'https://api.appstruct.cloud/v1/docs/mcp'

Which MCP servers does AppStruct provide?

AppStruct provides three remote Model Context Protocol servers for Docs, Sheets and Slides. Compatible AI clients connect over Streamable HTTP using a product-specific API key in an Authorization: Bearer header. Each server exposes the read or write tools permitted by that key and operates on resources owned by its account.

Question	Answer	Details and source
What does the Docs MCP server do?	The /v1/docs/mcp endpoint lists, reads and searches owned documents. With write access it creates documents and edits plain text. Use the Docs browser editor for rich formatting, tables, images and page layout.	Published Docs API specification →
What does the Sheets MCP server do?	The /v1/sheets/mcp endpoint lists workbooks and reads cells or A1 ranges. With write access it updates values and formula text, appends rows and changes sheets. Calculated formula results require the browser spreadsheet editor.	Published Sheets API specification →
What does the Slides MCP server do?	The /v1/slides/mcp endpoint reads owned presentations, slide text and optional notes. With write access it creates decks and changes slide content or structure. The API does not export PDF/PPTX or edit images, geometry, fonts or animation.	Published Slides API specification →
How can I check access before allowing changes?	Start with the matching product’s read scope and inspect a real tool response. Use list_documents, sheets_list_spreadsheets or list_presentations. A saved configuration alone does not prove that the key works or that a file is reachable.	Read-only prompts and expected results →

Product reference by AppStruct. Checked November 4, 2026 against the linked product guides and API references. Plan eligibility and third-party requirements should be checked for your own workflow.

Choose the product and the access it needs.

AppStruct exposes remote MCP endpoints over Streamable HTTP. Use a client that can send an Authorization header, such as Claude Code. Each product has its own API-key settings; connect the products you need individually.

This choice recommends scopes. It does not create a key or change any existing permission.

Create a Docs API key

Docs connection

Endpoint

https://api.appstruct.cloud/v1/docs/mcp

Transport

Streamable HTTP

Recommended scopes

docs:read

Claude Code · run in your terminal

claude mcp add --transport http appstruct-docs https://api.appstruct.cloud/v1/docs/mcp --header "Authorization: Bearer YOUR_APPSTRUCT_DOCS_API_KEY"

The example contains a placeholder, never a real API key.

Another compatible client needs the same endpoint and this header: Authorization: Bearer YOUR_APPSTRUCT_DOCS_API_KEY. Follow that client’s HTTP configuration format.

1. Create the key in your account

   Open the selected product’s API settings, choose the scopes shown above and save the key when it is displayed. The plaintext is shown once. This page does not ask you to paste it.

2. Replace the placeholder locally

   Put your key into your client’s configuration on your own device. Keep credentials out of shared repositories. The read-only and read + write commands look the same because permissions belong to the key, not the command.

3. Check the connection before editing

   In Claude Code, open /mcp and check the server’s status. Start by listing or reading a resource. Copying or registering a command alone does not verify the credentials or run a tool. Use the first-read checks below.

Test the connection with a file list.

Use the matching product’s read scope and ask your assistant to run one of these tools. Review the actual tool response: a saved configuration or an assistant’s promise to connect is not a successful read.

Check Docs access

list_documents

Use list_documents to list the first page of documents I own. Show their IDs and titles. Do not create or edit anything.

Expected response

Document IDs and titles. This lists the library; use get_document with a returned ID to read the document text.

Continue to the Docs workflow →

Check Sheets access

sheets_list_spreadsheets

Use sheets_list_spreadsheets to list the first page of spreadsheets I own. Show their IDs, names and sheet tabs. Do not change anything.

Expected response

Spreadsheet IDs, names and sheet tabs. Choose a returned workbook ID and an existing tab before reading a bounded A1 range.

Continue to the Sheets workflow →

Check Slides access

list_presentations

Use list_presentations to list the first page of presentations I own. Show their IDs and titles. Do not create or edit anything.

Expected response

Presentation IDs and titles from the key’s account. Use get_presentation with a returned ID to inspect the slide content.

Continue to the Slides workflow →

A successful empty list can mean there are no owned files in this view. If you expected a file, check ownership, product and pagination before creating anything.

A document MCP server for drafts and targeted text edits.

Connect an assistant to documents in your AppStruct Docs library. Find a brief by the words inside it, read the current draft, or create a separate document from an outline. The result remains a document you can open and review in the browser editor.

What an assistant can do

Read access: list owned documents, read their text and search titles or document contents.

Write access: create a document, insert text, replace matching text and rename a document. Grant read access too when the assistant needs to inspect an existing draft.

Current limits to plan around

• MCP works with document text. New content is plain text, not HTML or rich formatting; it does not create styled tables, images or page layouts.
• Read the current document before editing it. Text positions can change after an insertion, and a broad replacement can affect more than the phrase you intended.

Turn meeting notes into a separate project brief

Find my document that mentions the launch checklist. Read it and propose a project brief with goals, open questions and next steps. After I approve the draft, create a new document; leave the original notes unchanged.

1. Search for the relevant document and read its text before drawing conclusions. Ask for clarification if several documents match.
2. Review the proposed brief in the conversation. With a read + write key, the assistant can create the approved text as a new, clearly named document.
3. Open the new brief in Docs to check the wording and apply headings, layout or other formatting in the editor.

Use a Docs MCP Server to Turn Meeting Notes into a Project Brief

A spreadsheet MCP server for ranges and repeatable updates.

Let an assistant inspect a workbook, read specific A1 ranges and write approved changes back to AppStruct Sheets. This suits a project tracker or a regularly updated table where you want the assistant to work with specific cells rather than another pasted copy.

What an assistant can do

Read access: inspect spreadsheets and sheets, search cells, read one or several ranges, and read existing cell formatting.

Write access: write values or formula text, append rows, update several ranges in one save, and add or delete sheets. Formatting is readable through MCP, not writable.

Current limits to plan around

• The API returns formula text, not calculated results. Formulas written through MCP are evaluated when the spreadsheet is opened; this is not a server-side calculation engine.
• Protected ranges retain their stored values unless the key also has sheets:write-protected. That extra scope is separate from ordinary write access and is not recommended by this setup helper.

Review and update a project tracker

Read Project!A1:F30 from my tracker. Identify tasks with a missing owner and propose updates using these assignments. Show the exact cells first; write only the changes I approve, then read those cells back.

1. Identify the workbook and sheet, then read the bounded range. Keep headers and row identifiers in view so an update reaches the intended task.
2. Approve the proposed values and addresses. A read + write key allows the assistant to write the selected ranges and verify the stored values afterwards.
3. Open the workbook in Sheets to review the result. If the changes include formulas, inspect their calculated results in the spreadsheet client.

Use a Sheets MCP Server to Track Service Requests

A presentation MCP server for slide content and structure.

Connect an assistant to AppStruct Slides to find a deck, read its slide text and speaker notes, or build a new presentation from an outline. Continue in the browser editor when you are ready to review the layout, add visuals and prepare the final presentation.

What an assistant can do

Read access: list and search owned presentations, read a deck and inspect individual slides, their text slots and optional speaker notes.

Write access: create presentations, add and reorder slides, update text or notes, duplicate or skip slides, and rename a deck. Read access lets the assistant inspect before changing it.

Current limits to plan around

• The API does not export PDF or PPTX, insert images, or edit geometry, fonts, colours or animation. Browser-editor export is a separate capability.
• Avoid API edits while the deck is open for editing: an editor save can overwrite them. Close the editor before writing through MCP and reopen it afterwards.

Create a first draft of a project update

Create a five-slide project update from these notes using titleBody layouts: goal, progress, risks, next steps and decisions needed. Keep each slide concise and put supporting detail in speaker notes. Leave the images and visual styling for my review.

1. Provide the source notes and agree on the slide outline. Creating the deck requires write access; use a read + write key to inspect the result as well.
2. Create a separate presentation, then read its slides and check that every statement is supported by the notes. Revise text or slide order where needed.
3. Open Slides to review the visual result, add images and finish the design. Use the browser editor for supported presentation exports.

Create a Project Status Update with a Slides MCP Server

Find the symptom. Check the saved state.

Start with the error or tool response you can observe. These checks separate authentication, permissions and file access from what happens after a write.

The connection returns 401 or an invalid-key error

Check first

Check that the endpoint and key belong to the same AppStruct product. Confirm that the client sends Authorization: Bearer followed by the actual key, with the placeholder removed.

Next step

Check the key’s status in that product’s API settings. An expired or revoked key will not authenticate. Update the client configuration locally, reconnect and repeat the read-only check.

Read tools work, but write tools are missing

Check first

Tool discovery follows the key’s scopes. A docs:read, sheets:read or slides:read key exposes read tools; selecting “Read + write” on this page does not change an existing key.

Next step

For an approved editing task, use a key with that product’s read and write scopes. Reconnect the client so it discovers the available tools again. If a request returns 403, inspect the required scope in the error before changing access.

The list is empty, or a known file is missing

Check first

These APIs reach files owned by the key’s account. A shared file or share link does not grant API-key access. Check that you are looking in the same account and product as the key.

Next step

Page through a longer library and check whether the file is in the trash. Use the returned resource ID for later calls. An empty list alone is not a reason to create another copy of the file.

A write timed out and the saved result is unclear

Check first

A timeout does not prove that the write failed. Repeating a create or append request can produce another document, presentation or set of rows.

Next step

List the library after an uncertain create, or read the affected document, slide or cell range after an edit. Compare the stored result with the approved change before retrying. Keep resource IDs and stable row identifiers in the workflow.

A Sheets formula is returned as text

Check first

The Sheets API reads stored formula text, not a server-calculated result. Writing a formula through MCP does not by itself evaluate the workbook.

Next step

Open the workbook in the Sheets browser editor and inspect the calculated cells. Check the formula’s sheet names and references there before using the result in a decision.

A Slides edit disappears after an editor save

Check first

An open presentation editor can save its earlier state over an API change. Avoid editing the same deck in the browser and through MCP at the same time.

Next step

Close the presentation editor before an MCP write. Read the deck back through MCP, then reopen it in Slides to review the saved text and layout.

After correcting the configuration, repeat a read-only check before resuming an editing workflow.

Connect the right account. Keep the review step.

Each key reaches resources owned by its AppStruct account. Files shared with that account and resources opened by a share link are outside these APIs. A Docs connection also does not grant access to Sheets or Slides.

Start with read access

A read-only key exposes read tools, not write tools. Use it for questions and inspection; create a key with the additional write scope when a workflow needs changes. Review proposed replacements, cell addresses and deletions before approving them in your client.

Match the client’s authentication

This guide uses API-key authentication. A client that only accepts an OAuth sign-in needs a different connection flow; pasting the endpoint alone will not supply a key. Check your client’s supported authentication before configuring it.

Read back the result

Give the assistant a specific resource and a bounded task. Inspect the saved content after a write and review the final document, workbook or deck in its editor. An assistant’s confirmation is not a substitute for checking the work.

Explore the AppStruct workspace