How AI connects to apps and tools | MCP explained

What are you allowing an AI to do when you connect another app? Follow a genuine, small Notion example: read an invented equipment list, change one tripod's availability, then read it again to verify the saved result. We separate the AI application, its connection and the outside service; explain MCP briefly; and distinguish installing, connecting, permitting and verifying. CHAPTERS 00:00 One tripod, one useful update 00:19 The application, connection and outside service 00:35 Where MCP fits 01:24 Origin, maintainers and the safety boundary 01:38 Our genuine Notion example 02:02 The requested change 02:22 Read the saved result again 02:46 Four separate facts 03:01 Permissions and data destinations 04:01 Three questions before you trust it DEMONSTRATION INSTRUCTIONS The production instruction authorised one private Notion page called “Thoth Protocol V009 demo”, containing invented equipment-lending records. It asked us to read the page through the existing connection, make one reversible change to an item's availability, and read the page again. Page created: Invented equipment-lending records for an educational demonstration. No real people or bookings. Equipment: • Blue tripod — Availability: Available • USB microphone — Availability: On loan • LED panel — Availability: Available Read: fetch that exact page. Change: on that page only, replace “Blue tripod — Availability: Available” with “Blue tripod — Availability: On loan”. Leave everything else unchanged. Verify: fetch the same page again and compare all three records. Observed: the new fetch returned the tripod as On loan. The microphone remained On loan and the LED panel remained Available. The update response returned the page identifier; no separate confirmation dialogue appeared. There were no failed demo attempts or additional repair prompts. The actual structured requests and raw responses are retained in the production package. The visible views are edited presentations of those real responses, not recordings of the Notion interface. This one task does not establish page-only account access. The installed connection's endpoint and protocol negotiation were not independently inspected. This is a connector demonstration; the MCP explanation is based on current official documentation. No monitor or automation was created. No private tracker content is shown. These are invented records, not real bookings. SOURCES — checked 6 October 2026 MCP architecture (current redirect: 2026-07-28) https://modelcontextprotocol.io/docs/... MCP specification and security principles https://modelcontextprotocol.io/speci... Current governance and maintainers https://modelcontextprotocol.io/commu... Original announcement, 25 November 2024 https://www.anthropic.com/news/model-... MCP joins the Agentic AI Foundation, 9 December 2025 https://blog.modelcontextprotocol.io/... OpenAI remote MCP guide (API behaviour is not every product's behaviour) https://developers.openai.com/api/doc... Notion MCP and supported tools https://developers.notion.com/guides/... https://developers.notion.com/guides/... Notion access and data guidance https://www.notion.com/help/notion-mcp https://developers.notion.com/guides/... Current Notion app eligibility, controls and disconnection https://help.openai.com/en/articles/1... Plans, account permissions, product controls and available actions can change. Check the connection you actually use. Original diagrams and original generated illustrations by Thoth Protocol. The equipment image and thumbnail are AI-generated illustrations, not app screenshots. Narration: Matt via ElevenLabs Eleven v4. Optional UK English captions supplied separately. No competitor footage, artwork or narration reused.