korrents
Scott Spence

What Scott Spence thinks about MCP

@scott-spence · 6 positions · On ppll ↗

Product engineer and Svelte consultant in the UK; writes about SvelteKit, coding agents and Linux at scottspence.com.

Scott Spence did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter MCP · Newest first
Topic
All 6MCP 3SQLite 1
Sort
NewestOldest

Only Scott Spence on MCP. See everyone on MCP

3 dated positions, 2026, in their own words. Our reading of what Scott Spence has said — not written or endorsed by them.

3 positions so far — this page is not yet offered to search engines.

  1. Our readingModels are good at using a CLI, and can run --help when they are unsure, so an MCP server is often unnecessary.

    Their wordsModels are good with a CLI, and they can run --help when they're unsure.

    ↗Give Coding Agents Your Project Docs With node:sqlite and FTS5scottspence.com

  2. 2 days earlier

  3. Our readingAn MCP server is still the right place to keep a tool's secrets or auth, even though MCP is not the default choice for every tool.

    Their wordsThat doesn't mean MCP is dead. When a tool needs secrets or auth, an MCP server is still the right place to keep them

    ↗I Built 21 MCP Tools. These Are the 2 I Still Usescottspence.com 1st of 3 in this piece

  5. Our readingModels have improved enough that on many occasions an agent no longer needs an MCP server for the kind of tool people used to build one for.

    Their wordsBut for the kind of tools I was building, the models have come on so well that on a lot of occasions there isn't really a need for one.

    ↗I Built 21 MCP Tools. These Are the 2 I Still Usescottspence.com 2nd of 3 in this piece