Use Archinet Projects with your AI assistant

01

Choose your assistant

You’ll need an active Archinet account with the appropriate permissions, and an AI app that allows custom remote MCP connections. On a company account, your workspace administrator may need to enable or add the connection for you.

Open the instructions for your app. The Archinet sign-in steps that follow are the same for every app.

ChatGPT Web

In ChatGPT, open Settings → Security and login and enable Developer mode, if your account or workspace permits it.
Open ChatGPT Plugins and select the + button to create a developer-mode app.
Name it Archinet Projects. For the connection, enter https://mcp.archinet.net/mcp.
Choose OAuth authentication. If asked how to register the connection, choose Dynamic Client Registration (DCR). Archinet does not require you to enter a client secret or API key.
Create the connection and complete the Archinet sign-in and permission screen below.
In a new conversation, use the + menu, choose Developer mode and select your Archinet Projects connection.

Developer mode is available to ChatGPT Plus, Pro, Business, Enterprise and Education accounts, on the web. On a workspace account an administrator may need to enable it first. For the ChatGPT desktop app, use the Codex instructions below instead.

Menu names and availability can vary by account. OpenAI’s current setup instructions ↗

Claude Web, desktop or mobile

Open Customize → Connectors.
Select + → Add custom connector. Enter Archinet Projects as the name and https://mcp.archinet.net/mcp as the URL.
Leave the optional OAuth client ID and client secret fields empty. Select Add, then Connect to sign in to Archinet.
Complete the permission screen below. In your conversation, open + → Connectors and enable Archinet Projects.

Custom connectors are available on every Claude plan, including Free, which is limited to one custom connector. The connection belongs to your Claude account, so once added it is available in Claude on the web, in Claude Desktop and in the mobile apps.

On a Team or Enterprise workspace, an owner adds the connector first under Organization settings → Connectors → Add → Custom → Web. You then find it under Customize → Connectors, select Connect and sign in with your own Archinet account.

Claude’s current custom connector instructions ↗

Codex Command line, IDE or ChatGPT desktop app

If you use the Codex command line, add the server and start sign-in:

codex mcp add archinet --url https://mcp.archinet.net/mcp
codex mcp login archinet

Follow the browser sign-in, approve access and return to Codex. Start a fresh conversation and use /mcp to check the connection.

In the IDE extension, open the gear menu and choose MCP servers → Add server. Choose Streamable HTTP, enter the server URL, save and restart the extension. Select Authenticate when prompted.

In the ChatGPT desktop app, open Settings → MCP servers → Add server. Choose Streamable HTTP and enter the server URL. In the composer, type /mcp to see connected servers.

The Codex command line, the IDE extension and the ChatGPT desktop app share one configuration, so adding the server in one makes it available in the others.

OpenAI’s current Codex MCP instructions ↗

These are custom connections you add to your AI app. If you cannot find the option, check the app’s current instructions or ask your workspace administrator.

02

Your assistant opens the Sign in to continue page. Check that the Archinet address begins with https://mcp.archinet.net/. Use the same account you use at projects.archinet.net.

Archinet password: enter your existing Archinet email address and password, then select Sign in.
Microsoft Login: choose Sign in with Microsoft 365 if your Microsoft account is already linked to Archinet. If it is not linked, follow the prompt to connect it at projects.archinet.net first, then restart the connection from your AI app.

If you are already signed in to the MCP server, you may go straight to the permission screen. Enter your password on the sign-in page, not in the conversation with your assistant.

03

Review & allow access

The Allow [app name] to access Archinet? screen shows your account and the requesting app. Confirm that you started this connection, the account is yours and the return address belongs to your AI app. Select Allow access to continue, Cancel to stop, or Use a different account to switch accounts.

Your permissions stay in place

The assistant uses the tools as you. Your project access and document restrictions still apply. Editing and administration tools check your permissions for each action.

The app can stay connected

If the app requests ongoing access, the permission screen offers access for up to 30 days without asking again. Manage the connection in your AI app’s settings.

When the connection finishes, return to your AI app and make sure Archinet Projects is enabled for the conversation.

04

Ask your first question

Start with a simple connection check:

Use Archinet Projects to tell me which account I’m connected as, then list the active projects I can access with their names and numbers.

Or take the guided tour

This tour explores your projects and meetings without changing them. It asks before reading meeting minutes because those reads are recorded in the meeting owner’s audit trail. It ends with a short report you can share with Archinet support.

You're connected to Archinet Projects through an MCP connector. Give me a guided
read-only tour using my real data. Work through these steps in order.

1. Confirm which Archinet account and company I'm connected as.
2. List the active projects I can access. Use the summary or count tools for
   totals, including any completed or cancelled projects I can access.
3. Ask me to choose a project. Show its details, document counts by category and
   file type, members and companies, current announcements, recent activity,
   and my pending required downloads and responses.
4. Show a page of document metadata from that project, then search by a keyword
   or category I choose. Include filenames, dates and uploaders. Do not claim
   that a page of results is the full list or that you have read the files.
5. Show comments and download/notification activity for a document I choose.
6. List my pending required downloads and responses across projects. Page
   through all results if needed.
7. List meetings I can access, including meetings I recorded myself. Ask before
   reading one meeting's minutes or items: those reads are recorded in the
   meeting owner's audit trail. If I agree, summarize the decisions, action
   items and open questions. Preserve any unverified labels from the source.
8. For a meeting I recorded, list its saved versions and identify the newest
   and Final versions. Show my available meeting download templates. Ask before
   reading an earlier version, and do not restore, edit, finalize or share it.

Rules: use the Archinet tools rather than guessing. Never invent IDs or links.
Use summary/count tools for totals and check whether lists have more pages.
Do not post, edit, delete, change project membership or status, or change any
customer or invoice. Do not rename meetings, restore versions, mark minutes
Final, change meeting projects or change download templates.
Document tools return metadata, not file contents.
If a tool returns an error, show the exact error and continue where possible.

Finish with a short report of the tools called, what worked, what failed
(with the exact error text), and anything slow, confusing or unavailable.

Then try one of these. Replace the text in brackets with your project, document, meeting or search term. You do not need to know tool names or project IDs.

Catch up on a project

Use Archinet Projects to brief me on [project name or number]. Include document totals by category, recent activity, announcements, project members and companies, and my pending required actions.

Find the right documents

In Archinet Projects, find documents in [project] whose filename, label or description contains [keyword]. Show filenames, categories, dates and uploaders. Check for more pages before calling the list complete.

See what needs your attention

Use Archinet Projects to list all my pending download and response requirements. Group them by project and include each document’s name and ID. Check for more pages.

Catch up on a meeting

In Archinet Projects, find [meeting] and summarize its minutes, decisions, action items and open questions. Keep any unverified labels. I understand that reading the minutes is recorded in the meeting owner’s audit trail.

Find a discussion

Use Archinet Projects to find comments mentioning [topic] on [document] in [project]. Include who said what and when.

Get an exact visible count

Use Archinet Projects to count the documents I can view in [project] and break the total down by category and file type.

Preview a minutes correction

For [meeting I recorded], list its versions and read the newest saved version. I understand that the read is audited. Preview [correction] with updateMeetingMinutes using preview=true and based_on_version set to version_returned from that read. Show the proposed changes and whether the result would be Draft or Final. Do not save or mark Final until I confirm.

Upload documents

Use Archinet Projects to prepare an upload to [project] in the [category] category, labeled [label]. Propose [people] for the e-mail notice. Give me the upload link, and do not tell me the documents are filed until you have checked.

Send a file you made

Upload [file] to [project] in the [category] category, labeled [label]. Send the file yourself through Archinet Projects, then give me the review link so I can choose who is notified and file it. Check the result after I file it.

Prepare to share a meeting

What can the connection do?

Projects and people: find projects, details, assignments, members, companies, categories and announcements. Summaries show recent activity and your pending actions.
Documents and activity: search document metadata, inspect upload groups, read comments, see download and notification history, and count documents or comments by supported categories. Project administrators can also review member activity.
Meetings: list meetings you recorded and meetings filed under projects you can access. Read minutes or collect action items, decisions and other meeting items. Count meetings by project, month, organizer or minutes status. For your own meetings, inspect version history, edit minutes or the title, restore an earlier version, mark minutes Final, and choose the project and download template. Your unfiled meetings are visible only to you.
Comments, announcements and documents: with the required permissions, post a comment or reply; add, edit or delete announcements; edit a document’s label, description or category; or delete a document. These tools do not replace a document’s file.
Uploads: prepare an upload of new documents to a project you can upload to. You choose who is notified and file it on an Archinet page; see Upload documents through your assistant.
Project administration: with project administration permission, add existing active users to projects, remove members, update project details, change the manager or administrator, archive a project or reactivate it. Cancelling a project requires Archinet admin or system Admin permission.
Archinet administration: the Archinet admin role can query clients, licensed systems, invoices, invoice totals and site statistics, manage customer records, and create or update invoices. Project administration alone does not grant these accounting tools.

Most lists are paged. Ask for all pages when you need a complete list, and use count or summary tools for totals. Completed and cancelled projects require archive, project administration or system-wide project access. Member-assignment lookups are narrower: you must belong to the project and have archive access for completed or cancelled projects, unless you have the Archinet admin role.

Document files: these tools return metadata, not PDF or text-file contents. Browsing document records does not record a download or complete a required-download task. Open the file on the Archinet website to read or download it.

Reading meeting minutes: by default, the tools return the Final version when one exists, otherwise the newest version. The person who recorded the meeting can also list its saved versions and request a specific version. The tools do not return quoted transcript lines. Reading minutes or meeting items is recorded as a download in the meeting owner’s audit trail. Items marked unverified should remain identified as unverified in the assistant’s answer.

Changes: most project and document editing tools work on active projects; archiving, reactivating and cancelling change project status. Meeting changes instead require ownership of the meeting. Adding a comment completes your own pending comment-required task; comments cannot be edited or deleted through these tools. MCP changes do not send notification emails, and invoice changes do not send anything to the customer. Uploads are filed, and their notice e-mail sent, only when you select the button on the Archinet page. Use the website for file replacement and workflows not covered by the tools.

Edit, restore and share your own meetings

Only the person who recorded a meeting can change it or inspect its version history. Project administrators and Archinet administrators do not gain editing rights to someone else’s meeting. The minutes-editing tools work with saved minutes; they do not generate minutes, change attendees or delete the whole meeting.

Check history: getMeetingVersions lists saved versions and identifies the newest and Final versions. Use getMeetingMinutes with a specific version to read it. Before editing, read the newest version, which may differ from the Final version returned by default.
Edit and preview: updateMeetingMinutes can reword, add, remove or reorder discussion topics, decisions, action items, next steps, open questions and reviewer notes, and rename the meeting. Use the item IDs from the version you read. Action-item owners must match an attendee name or be TBD; due dates use YYYY-MM-DD, with a separate field for wording such as “end of month.” A preview checks the proposed edit without saving it.
Save a new version: ask your assistant to use version_returned from the minutes read as based_on_version for both preview and save. If the tool reports newer minutes, read that version and review the proposal again. Saving creates a new version and preserves earlier versions. Changed items lose their transcript verification; unchanged items keep it.
Choose Draft or Final: editing Final minutes makes them Draft again unless the edit also requests mark_final=true. Use markMeetingFinal to mark a chosen saved version Final separately. Check the returned version and Final status: an edit can save successfully even if marking it Final fails. For a filed meeting, project readers see the Final version, or the newest version when none is Final, so saving a Draft can still change what they see.
Restore: restoreMeetingVersion copies an earlier version into a new latest version. It keeps the intervening history and the meeting’s current title. Restoration makes Final minutes Draft again; review the restored version before marking it Final.
File or unfile: setMeetingProject files your meeting under a project you are assigned to, or removes it from its project. Being able to view or administer a project alone is not enough to file a meeting there. Filing makes the minutes available to people who can access that project; unfiling makes the meeting private to you again and clears its project download-template choice. Confirm the destination and audience before filing.
Choose a download template: getMeetingExportTemplates lists the templates you can use. Choose one when setting the meeting’s project to set the default download template for project readers. A reader’s explicit template choice for a download can override it. Leaving the template unspecified keeps the existing meeting choice; when none is set, each reader’s default applies.

Preview applies to minutes edits. Restoring, marking Final and changing the project or download template take effect when their tools are called, so ask your assistant to wait for your confirmation first.

Upload documents through your assistant

Your assistant can prepare an upload of new documents to a project you can upload to. It never files them or sends the e-mail itself: on an Archinet page, you choose who is notified and who must download or respond, and you select the button.

Upload page link: the assistant prepares the upload (project, category, label, access, and anyone you asked it to notify) and gives you a link to the Archinet upload page. Open it while signed in. The project, category, label and access are already set, and the people the assistant proposed are ticked; change the ticks as you like. Add your files and select Upload Files. The link works for 60 minutes and only for your Archinet account.
Files the assistant already has: an assistant that can run programs and reach projects.archinet.net, such as Claude Code, can send files itself: up to 20 files of up to 200 MB each, with the website’s file rules. Once they have arrived, it gives you a review link. There you see the files, tick who is notified and who must download or respond, and select File and send the e-mail or Don’t file. The review link works for about a day.
Who gets the e-mail: as for any upload on the website, the project’s own address and you always get the upload e-mail, plus the people you tick. With restricted access, the documents are visible to those who get the e-mail (you, the project’s address and the people you tick) and to the project’s administrators and Archinet administrators, who can open restricted documents anyway.
Check the result: ask the assistant to check the upload. It reports what was filed, any file that did not arrive, who was e-mailed and whether the e-mail was sent.

Up to five uploads can be in progress at once; a link nobody opened stops counting when it expires. The assistant can cancel an upload until you open its upload page, or while its review page is waiting. Files that reached Archinet are kept even when an upload is not filed.

Example questions for administrators

Project activity: “Show each member’s uploads, comments, downloads and pending required actions for [project].”

Invoice reporting (Archinet admin): “Show paid and unpaid invoice totals by month for [year], including tax.”

Prepare a change: “Find [document] in [project] and propose changing its label to [new label]. Show the current and proposed values, then wait for my confirmation before updating it.”

05

Manage your connection

Open your AI app’s connector or MCP server settings and find the Archinet Projects connection.
Use the app’s disconnect or remove action to stop using that connection in the app. Remove any duplicate connections you no longer need.
To reconnect, add https://mcp.archinet.net/mcp again and complete sign-in and consent. Use Use a different account on the permission screen when switching accounts.

The previous server’s Connected apps page does not manage connections to this MCP server. Removing a connection in your AI app does not delete information already returned to a conversation. If you need access invalidated on the server, contact Archinet support.

If something doesn’t work

I opened the server URL and see an authentication error.

That is expected when you open the connection endpoint directly without signing in through an MCP client. Paste https://mcp.archinet.net/mcp into your AI app’s connection settings, then use its Connect or Authenticate action.

The assistant says it cannot access a project or document.

Ask which Archinet account is connected, then check the same project or document on the website. Restricted documents need specific access unless you administer the project. Completed or cancelled projects require archive, project administration or system-wide project access. Access to member assignments can be narrower than access to the project itself. Contact your project administrator if the website also denies access.

The app keeps asking me to sign in, or the connection expired.

Start Connect or Authenticate again from the AI app. Complete sign-in and consent in the same browser flow. If you canceled, waited too long, removed the connection or changed accounts, start a new connection request.

The assistant cannot read a PDF or another document file.

The new MCP server exposes document metadata, comments and activity, not file contents or file downloads. Open the document on the Archinet website. Meeting minutes are available separately through the meeting tools.

The assistant cannot find a meeting or its minutes.

You can see meetings you recorded and meetings filed under projects you can access. Another person’s unfiled meeting is private to them. A visible meeting may not have minutes yet. By default, the tools use the Final version or, if there is no Final version, the newest version. Only the person who recorded the meeting can inspect its history and read earlier versions.

The assistant cannot edit my meeting, or says the minutes changed.

Confirm that you are connected as the person who recorded the meeting. Admin permission does not bypass meeting ownership. Minutes must be available; deleted minutes cannot be edited. If the version has changed, have the assistant read the newest saved version, preview the revised proposal and ask for confirmation again. Do not bypass the version check to force an older proposal through.

If the edit saved but could not be marked Final, check the returned version and use the separate Final action after review; do not repeat the edit. If the server says changing minutes is unavailable, contact Archinet support with the exact error.

A tool refuses to make a change.

Check that you have permission for that action. Project and document changes generally require an active project; meeting changes require you to be the meeting’s owner. Some actions require project administration; customer and invoice tools require the Archinet admin role. Reading a record does not automatically give you permission to change it. Ask the assistant to show the exact error before trying again.

The new Archinet tools are missing.

First check that the connection uses https://mcp.archinet.net/mcp. If it still uses the previous server, update or recreate it and sign in again. Then refresh its tools in your AI app and start a new conversation. In ChatGPT, open the connection in Plugins and select Refresh; on a workspace, ask your administrator if you cannot refresh it or the new actions are not enabled. In Claude, start a new conversation; if the tools are still missing, disconnect and reconnect Archinet Projects in Claude’s connector settings (Customize → Connectors, or under Plugins where Claude shows Plugins in the sidebar instead of Customize). In Codex or Claude Code, restart the session or reconnect the server with /mcp. Reconnect if your app does not offer a refresh action.

An upload link says it expired, was made for another user, or can no longer be used.

Upload links work only for the Archinet account that made them. An upload page link works for 60 minutes, and the review link for files the assistant sent works for about a day. An upload page you already opened can be reopened until the upload is filed. Otherwise, ask your assistant to prepare a new upload. A link for an upload that was filed, cancelled or failed shows what happened instead of the upload form.

I cannot add a custom connector, or setup fails.

Confirm that your AI account and workspace allow custom remote MCP connections. Use the exact server address above and OAuth authentication. If the app reports an unsupported return address or callback, contact Archinet support with the app name and error message.

For any other error, send support the app name, approximate time, visible error and the step where it happened. Do not include your password or access tokens.

Still need help?

Tell us which assistant you use and where you got stuck.

Contact Archinet support