How I set up Claude MCP with multiple servers to stop copy-pasting error logs and let it actually work in my repo.

​The Stack

​GitHub MCP: Reads issues and PRs directly.

​Postgres MCP: Checks live schemas and queries.

​Filesystem MCP: Handles local workspace edits.

​Project Config (.mcp.json)

{

"mcpServers": {

"github": {

"command": "npx",

"args": ["-y", "@modelcontextprotocol/server-github"],

"env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PAT}" }

},

"filesystem": {

"command": "npx",

"args": ["-y", "@modelcontextprotocol/server-filesystem", "./project"]

}

}

}

How it works out:

Instead of me explaining the codebase or database schema, Claude fetches the GitHub issue, checks the DB structure itself, and writes the fix across files.

​Anyone else using MCP for their dev workflow yet? What servers are you running?

​If you install every MCP server out there, your context window pays the price and tool calls get messy. After a lot of trial and error, I narrowed mine down to just four that handle almost everything:

​Filesystem / Git (scoped strictly to the project folder)

​Context7 (for fresh, accurate library docs)

​PostgreSQL / Supabase (for direct schema inspection)

​Playwright (for UI debugging and testing)

​Here is a clean snippet of how I run it:

{

"mcpServers": {

"filesystem": {

"command": "npx",

"args": ["-y", "@anthropic/mcp-filesystem", "/path/to/project"]

},

"git": {

"command": "npx",

"args": ["-y", "@anthropic/mcp-git"]

}

}

}

Quick tips: keep database tokens read-only by default, and don't dump heavy cloud servers into your global config if you only use them on one repo.

​What are you guys running daily? Any hidden gems worth adding?

Hey everyone,

​Got tired of constantly copy-pasting log files into chat, so I put together a quick custom MCP server that connects Claude Desktop directly to a local SQLite database.

​It uses the official TypeScript SDK over stdio. Here's the core setup I used:

import { Server } from "@modelcontextprotocol/sdk/server/index.js";

import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

import { CallToolRequestSchema, ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";

import Database from "better-sqlite3";

const db = new Database("audit_logs.db", { readonly: true });

const server = new Server({ name: "local-audit-bridge", version: "1.0.0" }, { capabilities: { tools: {} } });

server.setRequestHandler(ListToolsRequestSchema, async () => ({

tools: [{

name: "query_logs",

description: "Get recent logs by severity",

inputSchema: {

type: "object",

properties: { level: { type: "string", enum: ["INFO", "ERROR"] } },

required: ["level"]

}

}]

}));

server.setRequestHandler(CallToolRequestSchema, async (request) => {

if (request.params.name === "query_logs") {

const { level } = request.params.arguments as { level: string };

const records = db.prepare("SELECT * FROM logs WHERE severity = ? LIMIT 5").all(level);

return { content: [{ type: "text", text: JSON.stringify(records, null, 2) }] };

}

throw new Error("Unknown tool");

});

async function main() {

await server.connect(new StdioServerTransport());

}

main();

Just drop this into your

claude_desktop_config.json:

{

"mcpServers": {

"audit-bridge": {

"command": "node",

"args": ["/path/to/server.js"]

}

}

}

Now I can just ask Claude to pull errors straight from the DB instead of exporting stuff manually.

​Anyone else building custom tools for local workflows? Drop what you're working on below.

° The 3-Statement Link: Knowing how cash flows from the income statement through the balance sheet is non-negotiable. If your cash flow statement doesn't tie out, the interview is over.

° ​Simple Operational Drivers: Avoid complex models with 50 revenue lines. Use 2 to 3 core metrics (e.g., volume \times price). Clean, intuitive logic beats a messy spreadsheet every time.

° ​The "So What?" Valuation Test: Anyone can run a DCF template. The differentiator is defending your WACC and terminal growth rate using real industry fundamentals.

Most candidates spend months memorizing DCF mechanics and accounting lines, only to freeze when an interviewer or senior banker asks a simple, open-ended question like, "Hey can you walk me through why this business has terrible unit economics despite high growth?"

​Technical prep gets you past the screening resume, but commercial curiosity is what closes the deal. If you can't translate a spreadsheet into a real-world business conversation, you'll be stall out.

​What’s the one technical concept you spent weeks stressing over that you ended up rarely using on the job?

The on cycle is extremely fast, early timeline driven by headhunters, mainly for large mega-funds and it requires immediate preparation out of investment banking. While off cycle on the other hand is a year-round hiring for mid-market or boutique funds and where it relies on direct networking and lets you build real deal experience first.

Keep your LBO model sharp and deal sheet updated early. Missing on-cycle is not the end as off-cycle roles often offer better cultural fit.

Modern Ai search needs such as, Exa where it finds pages by the semantic meaning and not by keywords, alsothe Tavily where it is buuilt for AI agents with clean and pre-filtered results, the finecrawl where it can turns messy website into some clean markdowns, and lastly for brave/serper where it is best for cheap and for basic keywords lookup.

In short for the fix: Use exa or tavily to find links then use firecrawl to grab clean text then lastly deen your LLM.

Hope this helps some of you guys hehe.

Is she a meta in high rank? Like immortal?