isakskogstad/personupplysning-mcp

Personupplysning MCP Server

MCP server för svensk företags- och persondata via Bolagsverket API och Supabase cache

Ett HTTP MCP-server som tillhandahåller sökfunktioner för svenska företag och hämtar detaljerad finansiell data från Bolagsverket, med lokal cache i Supabase för snabbare svar.

🚀 Features

• Företagssökning - Sök bland 1.85M svenska företag i lokal databas
• Företagsdetaljer - Hämta fullständig företagsinformation från Bolagsverket
• Årsredovisningar - Ladda ner och parsera iXBRL årsredovisningar
• Smart caching - Supabase cache-first strategi (30 dagar företagsdata, 7 dagar dokument)
• HTTP MCP Server - Publikt tillgänglig via Render deployment
• Local development - Stdio mode för lokal utveckling

📋 MCP Tools

🏗️ Architecture

┌─────────────┐         ┌──────────────┐
│   Claude    │ ◄─────► │ HTTP MCP     │
│   Desktop   │   SSE   │ Server       │
└─────────────┘         │ (Render)     │
                        └──────┬───────┘
                               │
                        ┌──────┴───────┐
                        │              │
                   ┌────▼────┐   ┌─────▼────┐
                   │Supabase │   │Bolagsver-│
                   │ Cache   │   │ket API   │
                   └─────────┘   └──────────┘

🛠️ Installation

Prerequisites

• Node.js 18+ och npm
• Supabase project (gratis tier fungerar)
• Bolagsverket API credentials (portal.api.bolagsverket.se)

Local Development

1. Clone repository:

git clone <repo-url>
cd personupplysning

2. Install dependencies:

npm install

3. Setup environment:

cp .env.example .env
# Edit .env with your credentials

4. Setup database:

npm run db:setup

5. Import company data (optional):

npm run db:import

6. Run in stdio mode (local):

npm run dev

🌐 Render Deployment

Deploy to Render

1. Push to GitHub:

git init
git add .
git commit -m "Initial commit"
git remote add origin <your-github-repo>
git push -u origin main

2. Create Render service:

   • Go to dashboard.render.com
   • Click "New +" → "Web Service"
   • Connect your GitHub repository
   • Render will detect render.yaml automatically

3. Configure environment variables:

Add these in Render dashboard (Environment):

NODE_ENV=production
MCP_TRANSPORT=http
SUPABASE_URL=<your-supabase-url>
SUPABASE_SERVICE_ROLE_KEY=<your-service-role-key>
BOLAGSVERKET_CLIENT_ID=<your-client-id>
BOLAGSVERKET_CLIENT_SECRET=<your-client-secret>

4. Deploy:
   • Render will automatically build and deploy
   • Your MCP server will be available at: https://your-service.onrender.com/mcp

Connect from Claude Desktop

Add to your Claude Desktop MCP config (claude_desktop_config.json):

{
  "mcpServers": {
    "personupplysning": {
      "type": "http",
      "url": "https://your-service.onrender.com/mcp"
    }
  }
}

📁 Project Structure

personupplysning/
├── src/
│   ├── index.ts              # HTTP/stdio MCP server
│   ├── clients/
│   │   └── bolagsverket-api.ts  # Bolagsverket API client
│   └── services/
│       └── company-data-service.ts  # Cache-first service layer
├── scripts/
│   ├── setup-supabase.ts     # Database setup
│   ├── import-parquet.ts     # Import 1.85M companies
│   └── download-annual-report.ts  # Test script
├── data/
│   └── sample-reports/       # Downloaded iXBRL files
├── supabase/
│   └── migrations/           # SQL migrations
├── render.yaml               # Render deployment config
├── .env.example             # Environment template
└── package.json

🔧 Configuration

Environment Variables

Cache TTL Configuration

Cache expiration kan konfigureras i src/services/company-data-service.ts:

this.cacheTTL = 30 * 24 * 60 * 60 * 1000; // 30 days company details
this.documentCacheTTL = 7 * 24 * 60 * 60 * 1000; // 7 days document lists

📊 Database Schema

Tables

• companies - 1.85M svenska företag (lokal kopia)
• company_details_cache - API-svar från Bolagsverket (30 dagar TTL)
• company_documents_cache - Dokumentlistor (7 dagar TTL)
• financial_reports - Parsad finansiell data från iXBRL
• api_request_log - Request logging och analytics

Storage

• company-documents bucket - Lagrar nedladdade iXBRL ZIP-filer

🧪 Testing

Run tests:

npm test

Test specific file:

npm test -- bolagsverket-api.test.ts

Test API connection:

npx tsx scripts/download-annual-report.ts

📝 Development Scripts

🔒 Security

• OAuth2 tokens cached with 1-minute safety buffer before expiry
• Service role key required for Supabase (never expose publicly)
• API credentials stored in environment variables only
• GDPR compliance - EU Render region (Frankfurt)
• No personal data persisted without consent

📈 Performance

• Cache hit rate: ~95% after warm-up
• Local search: < 100ms (Supabase full-text search)
• Cached company details: < 50ms
• Fresh API call: 1-3 seconds (Bolagsverket rate limits)
• iXBRL download: 2-5 seconds (depends on file size)

🐛 Troubleshooting

Health Check Fails

Check endpoint:

curl https://your-service.onrender.com/health

Expected response:

{
  "status": "healthy",
  "server": "personupplysning-mcp",
  "version": "0.1.0",
  "uptime": 123.45,
  "endpoint": "/mcp",
  "environment": {
    "SUPABASE_URL": "configured",
    "BOLAGSVERKET_CLIENT_ID": "configured"
  }
}

MCP Connection Issues

1. Check Render logs for startup errors
2. Verify all environment variables are set
3. Test health endpoint first
4. Check Claude Desktop logs (~/Library/Logs/Claude/)

Database Connection Failed

# Test Supabase connection
npx tsx tests/test-supabase.ts

Bolagsverket API 401/403

• Verify credentials in Render environment
• Check token expiry (should auto-refresh)
• Ensure OAuth2 scope: vardefulla-datamangder:ping vardefulla-datamangder:read

📜 License

MIT

🤝 Contributing

Contributions welcome! Please follow these steps:

1. Fork the repository
2. Create feature branch (git checkout -b feature/amazing-feature)
3. Commit changes (git commit -m 'Add amazing feature')
4. Push to branch (git push origin feature/amazing-feature)
5. Open Pull Request

📧 Support

For issues or questions:

• Open a GitHub issue
• Check existing issues first

Built with: TypeScript, MCP SDK, Supabase, Bolagsverket API Deployed on: Render (EU region - Frankfurt)