Claude Integrations

That "Allow for this chat" pop up should be optional. It ruins the entire MCP experience. Maybe make it automatic for non-mutating MCP tools.

Anyone have any data on how effective models are at leveraging MCP? Hard to tell if these things are a buggy mess or a game changer

Integrations are nice, but the superpower is having an AI smart enough to operate a computer/keyboard/mouse so it can do anything without the cooperation/consent of the service being used.

Lots of people are making moves in this space (including Anthropic), but nothing has broken through to the mainstream.

I think all the retail LLM's are working to broaden the available context, but in most practical use-cases it's having the ability to minimize and filter the context that would produce the most value. Even a single PDF with too many similar datapoints leads to confusion in output. They need to switch gears from the high growth, "every thing is possible and available" narrative, to one that narrows the scope. The "hallucination" gap is widening with more context, not shrinking.

Had been planning a custom mcp for our orgs’ jira.

I’m a bit skeptical that it’s gonna work out of the box because of the amount of custom fields that seem to be involved to make successful API requests in our case.

But I would welcome, not having to solve this problem. Jira’s interface is among the worst of all the ticket tracking applications I have encountered.

But, I have found using a LM conversation paired within enough context about what is involved for successful POSTs against the API allow me to create update and relate issues via curl.

It’s begging for a chat based LLM solution like this. I’d just prefer the underlying model not be locked to a vendor.

Atlassian should be solving this for its customers.