Connect Claude or ChatGPT to TekStacks, then ask it things like "who has laptop IT-1042", "what is on port 12 of the core switch", "assign the spare ThinkPad to Dana and note the charger", "which certificates expire this month" or "pull up Stephan's onboarding checklist and let's work through it one by one".

Overview

An assistant connects with one address, https://api.tekstacks.com/mcp, the same for every company. You sign in to TekStacks as usual and allow it, and from then on it acts as you: it sees and changes only what you can in the app, in your company, and every change it makes is recorded in Activity under your name with the assistant beside it, such as "Dana Lee via Claude".

What it can do:

• Find and read equipment and who holds it, employees, services, software and license seats, documentation pages, snippets, changes, checklists, tasks and renewals, and the network: VLANs, subnets and their free addresses, racks, ports and cables traced end to end.
• Change what you can change: add and edit equipment and employees, assign, lend, check in and move equipment, give and take back seats, record a renewal, add and edit network records, write, file in folders, pin and archive documentation pages, start checklists and tick steps, record changes and mark them done, approve a change if your role approves changes, and add and complete tasks.
• Keep your lists if your role manages them: add, rename or edit, and archive or unarchive locations, departments, accessories, vendors, statuses, equipment types and makes, custom fields and, with Manage tag series, tag series. So "add Sam to the new Denver office in Finance" works even when Denver and Finance are not on your lists yet. It never deletes or merges a list entry.

What it can never do: see the Vault, license keys or file share links, delete anything, merge types or makes, upload files, or change users, roles or company settings.

Note: Everything TekStacks gives an assistant is your company's data, typed by people. TekStacks tells every assistant never to follow instructions it finds in that data, only yours.

Requirements

• Permission: Connect an AI assistant. Every built in role has it; an Admin can take it away from a role on Roles to keep assistants out.
• Claude or ChatGPT, on an account that can add custom connectors (also called apps). Which of their accounts include this is up to them.

Steps

Connect Claude

1. In Claude, open Settings, then Connectors.
2. Click Add custom connector.
3. Enter the name TekStacks and the URL https://api.tekstacks.com/mcp, then click Add.
4. Click Connect next to TekStacks. A TekStacks sign in page opens.
5. Enter your company's TekStacks address and continue, then sign in as you usually do (password and code, Microsoft or passkey).
6. Check what the page says Claude could do as you, and click Allow. You are taken back to Claude.
7. In a chat, open the tools menu and make sure TekStacks is turned on, then ask your question.

Connect ChatGPT

1. In ChatGPT, open Settings, then Apps and connectors (it may be called Connectors).
2. Under Advanced settings, turn on Developer mode if your workspace asks for it to add your own connector.
3. Click Create (or Add connector).
4. Enter the name TekStacks and the MCP server URL https://api.tekstacks.com/mcp, choose OAuth for authentication, and click Create.
5. A TekStacks sign in page opens. Enter your company's TekStacks address, sign in as you usually do, check what ChatGPT could do as you, and click Allow.
6. In a chat, choose TekStacks from the tools or connectors menu, then ask your question.

Let reads through, and keep changes on ask

Every TekStacks tool tells your assistant whether it only reads or changes something, and every change is marked as one that needs your say. Most assistants let you choose per tool:

• In Claude: in Settings, Connectors, open TekStacks and set the read tools (search, get, read, list) to Always allow, and leave every tool that adds, edits, assigns or disposes on Needs approval.
• In ChatGPT: when it first asks to use a TekStacks tool, approve reads for the conversation, and keep approving each change one at a time.

Whether an assistant follows these settings is up to the assistant. Before it changes anything, read what it says it is about to do. Disposing of equipment and marking someone as left are final in TekStacks, and the assistant is told to say so first.

Work through a checklist

Ask for the checklist by the person's name, such as "Pull up Stephan's onboarding checklist and let's work through it one by one." The assistant finds it, then takes the open steps in order: it says what each step is, asks, and ticks it only when you say it is done, never ahead and never several at once. A step it cannot tick for you, such as disposing of equipment or a drive wipe it does not have the date and method for, it says so plainly.

Write a checklist template

With Edit checklist templates, the assistant can add or change a checklist template: "Make a new location opening checklist: order the circuit, set up the firewall, label the rack." It shows you the steps in order before saving. To change a template it reads it first and sends the whole list of steps back, so it can reorder, add or remove steps in one change. Checklists already started keep their own steps.

Details that have no field

When you give an assistant details TekStacks has no field for, such as a laptop's graphics, display or color, it does not tuck them into the notes on its own. It asks whether to put them in the notes or to keep them as custom fields, and with your yes adds the fields that do not exist yet, named plainly (Graphics, Display, Color) and for that type of equipment unless you say otherwise. Adding a field needs Manage statuses, locations, departments, vendors and custom fields; without it, the assistant says so and offers the notes.

Add many records at once

Give the assistant a spreadsheet, a screenshot or pasted text and it can add or edit many records in one go: "Here is a screenshot of our IPs, add them to the 10.20.1.0/24 subnet." It reads the list, shows it to you in one message to check or correct, then saves it in one change you approve once, instead of asking you about each address. This works for anything it can add or edit: equipment, employees, addresses, subnets, VLANs, locations, vendors and the rest.

The records are saved all together or not at all. If any of them is refused (an address outside the subnet, a name that is not on your lists), nothing is saved, and the assistant tells you which ones need fixing so it can send the list again. Each record still gets its own entry in the activity log, and your plan's limits count the whole list.

Locations, vendors and their contacts

You can paste a location list or a vendor's contact sheet and have the assistant record it: "Add Westside Office at 410 Oak Street, Peoria IL, phone (309) 555-0140, branch manager Brandon Smith, with its 10.20.0.0/24 subnet and its Comcast internet circuit." It fills in the location's address, phones and manager, adds the subnet and the circuit, and puts the provider's customer service and billing numbers on the vendor as Support and Billing contacts.

The branch manager has to be one of your employees, named by email or full name. If they are not in TekStacks yet, the assistant asks you first, then adds them as an employee (asking about their email and onboarding, as for anyone new) with the job title Branch Manager at that location, and sets them as its manager. It never adds someone on its own.

When it changes a vendor's contacts it reads the current list first, since the list it sends replaces the one there.

Bookmarks into Links

Give the assistant your browser's bookmarks export (the HTML file Chrome, Edge or Firefox saves) or paste a list, and it adds them as links in one go: it reads each name and address, uses the folders as categories, leaves out anything that is not a web address, and shows you the list to check first. It never asks for or stores a password; tell it where each password is kept if you want that noted. See Links.

Turn a document into documentation

Share a Word document with the assistant, such as a setup guide full of screenshots, and ask it to make documentation pages from it. It writes the pages and marks where each image goes, since it cannot carry the images itself, then gives you a link to upload the document.

1. Open the link while signed in to TekStacks, within the hour. It shows the pages and how many images each is waiting for.
2. Click Upload the document and drop the same .docx file (up to 50 MB).
3. The images go into the pages where the assistant marked them, and each page keeps its earlier text in its revisions. The link's page then lists what was filled and anything left out.
4. Tell the assistant it is uploaded. It checks the pages and fixes anything left.

The document itself is not kept: TekStacks takes the images out and deletes it. The link works once, and only for you. Images Word saves in formats a browser cannot show (EMF, WMF, TIFF), pictures linked from a website and images over the attachment limit or your plan's largest file are left out, and the assistant is told which ones.

Virtual machines in one sentence

The assistant can add a virtual machine with everything about it in one go: "Add a VM called FS-02 in the Main cluster on ESX-01, 4 vCPU, 16 GB, Windows Server 2025, 10.20.1.40." It names the cluster and host the way you do, records the address in the subnet that holds it, and shows you all of it before saving. It can also add clusters, move a virtual machine to another host and decommission one once you confirm.

See and disconnect your assistants

1. Open your Security page from the profile menu.
2. Under Connected assistants, each one shows when you connected it and when it was last used.
3. Click Disconnect and confirm. It stops working at once; connect it again from the assistant to use it again.

An Admin sees every connection in the company in the Assistants column on Users, and can disconnect any of them from the person's row.

Notes

Note: Access ends at once when you disconnect, when an Admin disconnects it or turns your account off, when your role loses Connect an AI assistant, or when your company is paused. Sign in lasts an hour at a time and renews on its own for 30 days of use.

Note: An assistant can make 120 tool calls a minute for you. Past that it is asked to wait.

If you belong to more than one company on TekStacks, connect each one separately: the TekStacks address you enter when signing in decides which company the assistant works in. If you do not remember it, click Forgot your TekStacks address? Click here on the sign in page and TekStacks emails you a link to each company you belong to.

Troubleshooting

The sign in page says the assistant cannot be connected. It says why: your role does not allow connecting an assistant (ask an Admin), or your company is paused.

The assistant says it needs to sign in again. It was disconnected, your account was turned off, or its sign in ran out after 30 days without use. Connect it again.

The assistant says I don't have permission. It acts as you, so it can do only what your role allows in the app. Ask an Admin if you need more.

FAQ

Can the assistant see passwords in the Vault? No. The Vault, license keys and share links are never available to an assistant, whatever your role.

Can an MSP's assistant work in one client? Yes. It works across every client you can see, and you can ask it to work in one client by name.

Does the assistant get a copy of our data? It reads what it needs to answer each question, as you would in the app. What it keeps is up to the assistant's own settings and policies.

Can I use an assistant other than Claude or ChatGPT? Perhaps. TekStacks connects through MCP, an open standard, so any assistant that can add a remote MCP server and sign in to it may work with the same address and steps. Claude and ChatGPT are the ones TekStacks tests and supports.