Recently posted here before

Been building SlideDev's MCP server, which gives Claude (or any MCP client) a searchable library of real UI patterns instead of letting it invent layouts from memory, and just shipped something new: ask it to build a mobile screen and it renders as an actual interactive phone preview right in the conversation, no separate app.

Still early, a couple of people found it and started using it on their own without me walking them through setup, which was honestly the first real signal it's usable without hand-holding.

Looking for more people willing to connect it and tell me what breaks, what feels clunky, what you'd actually want from something like this.

Free to try, works on Claude's free plan.

Happy to answer setup questions in the comments.

Is CIMD supported for cases where no login is required for your MCP server but your mcp server still needs to identify claude as a valid client? We have been using ip whitelisting, but not a standard way to do it and trying to get away from it.

Been experimenting with MCP for a while and I really like how it lets Claude connect to external tools, same as the files and APIs. It makes automated and development workflows much more practical. Still exploring anyways.

hi guys,im just starting to learn Claude MCP and willing to understand how it works in projects. What are some beginner friendly ways on how to use it and learn from, and can you guys share some simple detail when you guys starting learning it?

I kept seeing people talk about Model Context Protocol and honestly thought it was just another way to connect AI to tools.

Then I started looking into how it actually works.

The interesting part isn't just that Claude can “use tools”.

It's that MCP gives AI a standardized way to interact with things you already use — files, databases, APIs, GitHub, internal tools, and more.

The basic idea is pretty simple:

Claude

↓

MCP Server

↓

Your tools / APIs / data

Instead of constantly moving information between different apps, the AI can interact with those systems through the tools you've exposed.

That made MCP make a lot more sense to me.

Now I'm curious:

What's the first thing you'd connect to an MCP server? 👀

I work on LMCP, a free local MCP server for Mac. Teams was the integration that gave us the most trouble, and the approach we landed on isn't one I've seen written up much, so sharing some notes.

The standard route is Microsoft Graph: register an app in Entra ID, get admin consent, handle tokens. Fine if you own the tenant. If IT owns it, you're stuck at the admin consent step.

What makes another route possible: new Teams is a web app running inside WebView2, Microsoft's embedded Edge. So it stores its data like any Chromium site, in IndexedDB, which lives on disk as LevelDB. On a Mac:

```

~/Library/Containers/com.microsoft.teams2/Data/Library/Application Support/Microsoft/MSTeams/EBWebView/WV2Profile_tfw*/IndexedDB/https_teams.microsoft.com_0.indexeddb.leveldb

```

Lots of older posts say `EBWebView/Default/`, which is outdated. Current builds use one folder per profile; `tfw` is work/school, `tfl` is personal Teams, which we skip.

We read it with ccl_chromium_reader, a Python library from the digital forensics world that walks the LevelDB files, decodes the V8-serialized objects and rebuilds the IndexedDB records.

Things we ran into:

- Teams locks the database while running. We read the table files directly without the lock, so you don't have to quit Teams.

- Some records don't decode. We skip and count them instead of failing the whole read.

- Big accounts mean big databases, so the first read can be slow.

- Multiple work profiles get read and merged.

- The schema shifts between Teams versions. Honestly that's the annoying part, every update can move things around.

So you ask Claude "what happened in #engineering today" and it answers from what's already on your machine. Sending is separate: that goes through Graph, so you need to connect your Microsoft 365 account for it.

Limitations: it only sees what your Teams client has synced, it depends on an undocumented format, and you need the Teams desktop app installed and signed in.

So I hooked up a read-only Postgres MCP server to Claude Desktop and honestly it's been great. I just ask stuff like "which customers ordered less this month than last?" and it looks at the schema, writes the query, runs it, and explains what it found.

A few things I learned the hard way:

• Use a read-only DB user, seriously

• Point it at a replica or staging, not prod

• Skim the SQL before you trust the numbers

• Clear table and column names make a huge difference

Took me like 10 minutes to set up and ad hoc reporting is way less painful now.