ChatGPT Plugin

Inline

Work chats in ChatGPT

Brand: Inline

Category: Productivity
Primary Subcategory: Team Chat & Messaging

Integration details

Description

Inline helps users find people and conversations, read and search scoped work chats, create threads, upload files, and send messages through ChatGPT.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Team Chat & Messaging
Secondary Subcategories: None listed
Brand: Inline
Access: Account required
First tracked: 2026-09-08
Tool count: 21
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Team Chat & Messaging

View Category

Listed in alphabetical order

Primary Subcategory

BalsioComing soonGet notified

DiscordbotComing soonGet notified

InlineComing soonGet notified

RingCentral ChatComing soonGet notified

RingCentral PhoneComing soonGet notified

Tools

21 tools agents can invoke

Create a private Inline thread containing you and the resolved participants, address them with named mentions, send one question, and return its receipt and replay cursor. This tool does not register Events or wait. Before an ask-and-wait send, establish host continuation support (ChatGPT Work or dots); regular ChatGPT chats require disclosing the limitation and accepting send-only. Use the host Events mechanism, which may be an Automations event trigger; events/subscribe is an MCP protocol method, not an Inline tool name. If the host accepts a replay cursor, use the returned cursor exactly. Otherwise register the exact message.created arguments, obtain host acknowledgement, then make one bounded messages.context read from the confirmed question messageId (before: 0, after: 50, includeAnchor: false, content: all) to check pre-registration replies. Disclose limited coverage if the read fails or fills its window; do not poll. Deduplicate overlapping replies by chatId/messageId and deliveries by eventId. Wait only after host registration, then read current context and continue the originating task. Stop this task's registration when a one-shot consultation is fulfilled. Creation and delivery are not idempotent; retain the chat ID and inspect uncertain outcomes before retrying.
conversations.ask
Use this tool to create a new Inline thread/chat in an allowed space or home threads. The audience follows the selected context: public threads in public spaces can be visible to anyone who joins. After creation, use messages.send or messages.send_batch with the returned chat.chatId.
conversations.create
Create a child of one resolved parent chat. The child inherits root-chat access plus its own direct/group grants. Participants added only to an intermediate child are not automatically inherited by descendants. participantUserIds adds access to a new child and cannot restrict root-chat access. Omit parentMessageId for an independent child, or supply it to create or reuse the reply thread for that message. An existing reply thread is returned without changing its title, description, emoji, or participants; these inputs apply only to new creation. Newly created private children include the creator directly; reuse does not repair older creator membership. Children outside spaces require home thread access. Use the returned chat.chatId for reading, sending, or forwarding.
conversations.create_subthread
Forward selected messages from a resolved source chat to a separately resolved destination chat, preserving the input order and media. Both chats must be approved by this grant. Resolve source and destination independently and inspect selected messages before forwarding. Returns ordered source/destination message ID pairs. Sending is not atomic or idempotent: an error may follow partial delivery, so inspect the destination before retrying to avoid duplicates. Forwarding headers follow server policy even when requested.
messages.forward
Return the Inline profile represented by this request's authenticated connection. The immutable user ID is stable across token refresh, reconnection, scope upgrades, and name or email changes.
account.profile
Use this tool after resolving a chatId to inspect conversation metadata, direct participants, explicit group-grant count, pinned message IDs, and parent/thread details before reading or sending. DMs also use chatId. Direct participants and group-grant count do not enumerate group members or inherited root-chat access and are not a complete audience list.
conversations.get
Use this tool when you need to inspect the current Inline MCP authorization, granted scopes, and allowed chat contexts before choosing read/write tools.
account.me
Use this tool after messages.search, messages.unread, or a known message ID to fetch a before/after window around that message in one chat. DMs also use chatId. Use messages.list for the latest context when there is no anchor message.
messages.context
Use this tool to extract file and media metadata from 1-20 known message IDs in one chat. Use messages.list with a files or media content filter first when message IDs are not known. DMs also use chatId.
files.get
Read exact message IDs from one resolved chat, including a DM. Results follow the requested order, with duplicate requests collapsed and unavailable IDs listed in missingMessageIds. Use this to inspect a selection before forwarding or verify known delivery receipts; use messages.context for surrounding discussion.
messages.get
Find the chatId for a person, DM, thread, or space chat before reading or sending. Query can be a contact name, @username, chat title, or chat ID. Use kind or spaceId to narrow approved conversations. For complete archive discovery, omit query, set includeSubthreads true and sort id, and continue with nextAfterChatId as afterChatId until null. This includes authorized hidden subthreads and requires an Inline server with includeSubthreads support. Filters apply before pagination.
conversations.list
Read recent context from one resolved chatId, including DMs. Results are newest first. Optional time, content, and sender filters scan at most 500 source messages. Continue with nextOffsetId as offsetId, including after an empty filtered page. Calendar days use UTC.
messages.list
Use this tool to list the spaces available to this MCP grant, including chat and unread counts. Use it before creating a space thread or narrowing conversation searches by team/workspace.
spaces.list
Use this tool to triage unread messages across all approved conversations. Results include chat metadata so you can follow up with messages.list on a specific chatId.
messages.unread
Read recent history and direct participants for one resolved Inline thread. Monitoring is reported only when the Events service confirms an active message subscription for this grant. Omit chatId to return an empty result; this does not list your workspace.
conversations.open
Search text within one resolved chatId, including DMs. Space-separated terms are ANDed. Results are newest first. Time and sender filters apply after the server's bounded search page, so an empty filtered page may have older matches: continue with nextOffsetId as offsetId until it is null. Calendar days use UTC. Use messages.list for filters without search text.
messages.search
Resolve a person by name, @username, or user ID across allowed DMs and spaces without exposing phone or email. Use userId for sender filters and participant selection; use dmChatId or conversations.list to resolve the chat ID required by current DM tools.
people.search
Use this tool to send an uploaded photo, video, or document to one chat. DMs also use chatId. Optional caption text is parsed as Inline Markdown. Delivery is recipient-visible and cannot be withdrawn through this tool. A public thread in a public space can be read by anyone permitted to join. Call files.upload first unless you already have an Inline media ID.
messages.send_media
Use this tool to send one recipient-visible text message to one resolved chatId; DMs also use chatId. Text is parsed as Inline Markdown. It cannot be withdrawn through this tool. A public thread in a public space can be read by anyone permitted to join. Use conversations.list first when resolving a person, DM, thread, or space chat.
messages.send
Use this tool to send an ordered sequence of normal, non-reply text and uploaded media items to one chat. DMs also use chatId. Text items are parsed as Inline Markdown. Every item has exactly two fields: type and content. Content is message text for type text, or an uploaded media ID for photo, video, and document. Use messages.send or messages.send_media instead when a reply target or silent delivery is needed. Delivered items are recipient-visible and cannot be withdrawn through this tool. A public thread in a public space can be read by anyone permitted to join.
messages.send_batch
Use this tool to upload one base64 payload or public HTTPS URL before sending media. Set sourceType to describe the required source value. It returns an Inline media kind/id pair for messages.send_media or messages.send_batch.
files.upload

FAQs

Inline ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Inline's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Inline alternatives on ChatGPT?

As of 2026-10-23, Inline competes with Balsio, Discordbot, RingCentral Chat, RingCentral Phone, Slack, Textxt, user_message, user_message_read and 1 more in ChatGPT Team Chat & Messaging, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.