Skip to content

Workspace (v2): use info from other external tools (GitHub, Notion, Canva etc) #1346

Description

@jeffpaul

What problem does this address?

The AI Workspace (#1004) lets you ask an assistant questions about your site, and it answers by looking through your posts, pages and terms. However, :alot: of the information people need lives outside WordPress: issues in GitHub, docs in Notion, contacts and deals in HubSpot or Salesforce, designs in Canva.

Today the assistant can't see any of that. If you ask "Draft a post about the bugs we fixed this month", it has no way to look at your GitHub issues. You have to copy and paste the information in yourself.

This is a deliberate choice in v1, because letting the assistant reach outside your site raises real safety questions:

  • Your site's content could be sent somewhere it shouldn't go. A post or comment could contain hidden instructions that try to trick the assistant into sending private site information to an outside service. v1 avoids this by only giving the assistant tools that stay inside the site.
  • Logging in to outside services is not solved yet. WordPress can store an API key for a service on the Connectors screen, but it can't yet do the "Sign in with..." flow that many services require, and a single stored key means everyone on the site acts as the same account.
  • The pieces aren't connected yet. The MCP Access and WebMCP experiments let outside AI tools connect into WordPress. Neither lets WordPress connect out to other services. Adding that is still being discussed in Add MCP client support to the adapter mcp-adapter#156.

What is your proposed solution?

Ship AI Workspace v1 as it is, focused on your own site. Then, as a v2 experiment, test ways for the assistant to use outside services safely. Ideas to try, roughly from smallest to largest:

  1. Start with one service, read-only. Add a couple of read-only tools for one service (GitHub is a good candidate: "search issues" and "read an issue"), using a key saved on the Connectors screen. This tests the experience and the safety controls before taking on anything bigger.
  2. Site owners choose what's connected. Nothing outside the site is available unless an administrator turns on that service and its tools, for example in the Abilities Explorer.
  3. People choose when to use it. Add an option next to "Site Context" and "General Knowledge" (for example "Site + connected services") so outside services are only used when someone asks for them.
  4. Show what's about to be sent. Before the assistant sends anything to an outside service, especially after it has read site content, show the person exactly what will be sent and let them approve it. Anything that would change something in an outside service goes through the same approve-before-it-happens step the workspace already uses for drafts.
  5. Keep a record. Log every call to an outside service in the AI Request Log, including which service and which tool was used.
  6. Connect through MCP. Once WordPress can act as an MCP client (Add MCP client support to the adapter mcp-adapter#156), let site owners add any service that offers an MCP server, instead of building each service by hand.
  7. Sign in per person. Explore "Sign in with..." (OAuth) support in the Connectors screen, so each person uses their own account and only sees what they're allowed to see in that service. This likely needs work in WordPress core.

Why is this important to you?

Most real work pulls from more than one place. An assistant that only knows what's on your site can help you write and organize content, but it can't help you report on a project, follow up on customers, or turn notes from another tool into a post. Connecting outside services is what turns the AI Workspace from a site search helper into an assistant that fits how people actually work. Getting the safety model right is the hard part, so we want community feedback on it before building further.

Related: #1287 (one AI agent across wp-admin), #1004 (AI Workspace v1), WordPress/mcp-adapter#156 (MCP client support).

I have searched existing issues and this is not a duplicate.

  • Yes

Activity

  1. added this to the 1.7.0 milestone on Nov 11, 2026
  2. moved this from Triage to In discussion / Needs decision in WordPress AI Roadmapon Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions