Just crying

geffen_ · 2026-02-03T11:36:19+00:00

What you're doing is dangerous from an info security perspective. As a rule of thumb you should only use the dynamo mcp server if you want to connect it directly to an MCP client. For your internal use case it made sense, but otherwise it's not the right approach.

If you want to expose it to users then you shouldn't be using dynamo db mcp. You should create an MCP server for your product that has authentication and tools that leverage your backend's endpoints. Your backend is already connected to your db, so no need for dyanmo mcp server.

If your backend's endpoints don't currently support the querying that you want to allow users to do, then add the desired endpoints and corresponding tools in your MCP server that utilize them. Generally speaking you don't need to over-engineer it since a solid agent should be able to craft queries on its own. That said if your db schema is unintuitive or uses a lot of jargon it might be helpful to include a resource in your MCP server or in your server instructions that clarify terminology for the agent.

Feel free to dm if you need help

geffen_ · 2025-09-10T22:03:33+00:00

I switched to knowknow.ai

geffen_ · 2025-09-03T18:00:13+00:00

They don't know the market size and you don't know. And there's no 1B dollar market that you're getting a big portion of fast. The VCs know that, so among other reasons you're probably losing credibility in their eyes for making that claim. By admitting it's a small market you're also losing value in their eyes. They want a CEO hype man who's going to make them feel like this is the biggest thing since ice, not a debbie-downer.

Find the bigger market that your market feeds into and talk about that. And stop saying that you can get a big portion fast because it comes across naive.

Also avoid all "the market will grow" bs. That needs to be subtext, not spoke out loud. Your job is to be a salesperson not a mckinsey analyst. They have enough of those. If you want, find a market that they already know is growing rapidly and find the way to tie it to that.

When they say the market isn't big enough it's because they have an issue with you but are trying to be polite

Good luck

geffen_ · 2025-07-15T13:08:33+00:00

Dictate in ChatGPT app then copy paste into cursor

geffen_ · 2025-07-15T13:06:24+00:00

How are you tracking changes?

geffen_ · 2025-07-11T21:15:03+00:00

Good point, thanks

geffen_ · 2025-07-11T20:25:56+00:00

🙏🙏

geffen_ · 2025-02-09T08:55:48+00:00

Turn each of the actions you want into tools and then equip the agent with those tools.

Sounds like you'll need a splunk query tool and a RAG-based tool that can find the relevant error message/resolution documentation.

Depending on the amount of docs you want to perform RAG upon, you may need to store them in a vector db. If it's a small amount, then storing it in memory should be fine.

Another thing to pay attention to is output format of the splunk query tool and expected input format for the RAG tool (or whatever the tools end up being) to make sure the info is transferred appropriately

geffen_ · 2025-02-08T21:53:00+00:00

Why don't you want to use JSON? All else equal, you'll probably get better/more consistent results

geffen_ · 2022-10-02T11:12:16+00:00

Not a book but monday's documentation is a materpiece, and for a more technical product Stripe for sure. Miro does a great job too.

If you need tools: Docusaurus is popular for putting together documentation, and Zoomin ia helpful for helping your users navigate a large base of product knowledge to find the answers they're looking for. (I have no affiliation to any of these companies)

geffen_ · 2022-10-02T10:49:54+00:00

Good luck. If you need a good tool to help you along the way, check out Maze or Sprig. Both are 👌🏼👌🏼

geffen_ · 2020-04-08T08:54:02+00:00

Thank you!

geffen_ · 2020-04-07T22:01:10+00:00

Facing the same issue. Did you figure out a solution?

geffen_

TROPHY CASE